data Static interface comparison
dbmcp
0.18.1 0.19.0
No policy-significant interface change detected.
View the upgrade review as Markdown
A shareable summary of this comparison for an issue, pull request or ticket. Select the text and copy it.
INTERFACE DIFF
What changed, tool by tool
- 0Added tools
- 0Removed tools
- 2Modified tools
- 0Input-schema changes
- 0Output-schema changes
- 0Declared authority changes
2 tools with recorded changes
explainQueryModifiedWhat changed
- explainQuery: description changed.
Why it could matter
- Models choose and call tools partly from their descriptions.
What to verify
- Spot-check that agents still select this tool as intended.
- Declared effect
- read → read
- Description
- PreviousReturn the execution plan for a SQL query to diagnose performance. Use this tool instead of running EXPLAIN directly through readQuery — it provides structured output. <usecase> Use when: - A query runs slowly and you need to understand why - Investigating performance bottlenecks - Planning index creation to optimize queries - Analyzing join methods, table scan strategies, and sort operations </usecase> <when_not_to_use> - Running actual queries → use readQuery, or writeQuery for data changes (not available in read-only mode) - Checking table structure → use listTables(detailed=true) </when_not_to_use> <examples> ✓ "Why is my SELECT on orders slow?" → explainQuery(query="SELECT ...") ✓ "Should I add an index?" → explainQuery with analyze=true ✗ "Run this SELECT" → use readQuery </examples> <safety> Set `analyze` to true for actual execution statistics (EXPLAIN ANALYZE). IMPORTANT: EXPLAIN ANALYZE actually executes the query! In read-only mode, only read-only statements are allowed with analyze. When analyze is false, returns EXPLAIN FORMAT=JSON output without executing. Only a single SQL statement is accepted. </safety> <what_it_returns> A JSON array of execution plan rows showing access methods, join types, row estimates, and costs. Long string values are cut and end in `…[truncated, N chars total]`, and rows past the response size cap are dropped and counted in `rowsOmitted`; when either happens the response carries `truncated: true` and a `hint`. </what_it_returns>
- CurrentReturn the execution plan for a SQL query to diagnose performance. Use this tool instead of running EXPLAIN directly through readQuery — it provides structured output. <usecase> Use when: - A query runs slowly and you need to understand why - Investigating performance bottlenecks - Planning index creation to optimize queries - Analyzing join methods, table scan strategies, and sort operations </usecase> <when_not_to_use> - Running actual queries → use readQuery, or writeQuery for data changes (not available in read-only mode) - Checking table structure → use listTables(detailed=true) </when_not_to_use> <examples> ✓ "Why is my SELECT on orders slow?" → explainQuery(query="SELECT ...") ✓ "Should I add an index?" → explainQuery with analyze=true ✗ "Run this SELECT" → use readQuery </examples> <safety> Set `analyze` to true for actual execution statistics (EXPLAIN ANALYZE). IMPORTANT: EXPLAIN ANALYZE actually executes the query, so only read-only statements are allowed with analyze. When analyze is false, returns EXPLAIN FORMAT=JSON output without executing. Write statements are rejected: the plan is fetched in a read-only transaction. Only a single SQL statement is accepted. </safety> <what_it_returns> A JSON array of execution plan rows showing access methods, join types, row estimates, and costs. Long string values are cut and end in `…[truncated, N chars total]`, and rows past the response size cap are dropped and counted in `rowsOmitted`; when either happens the response carries `truncated: true` and a `hint`. </what_it_returns>
Input schema
Input schema unchanged.
4 unchanged entries
(schema root)analyzedatabasequery
Output schema
Output schema unchanged.
6 unchanged entries
(schema root)hintrowsrows › [items]rowsOmittedtruncated
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
readQueryModifiedWhat changed
- readQuery: description changed.
Why it could matter
- Models choose and call tools partly from their descriptions.
What to verify
- Spot-check that agents still select this tool as intended.
- Declared effect
- read → read
- Description
- PreviousExecute a read-only SQL query. Allowed statements: SELECT, SHOW, DESCRIBE, EXPLAIN. <usecase> Use when: - Querying data from tables (SELECT with WHERE, JOIN, GROUP BY, etc.) - Aggregations: COUNT, SUM, AVG, GROUP BY, HAVING - Listing server variables or status (SHOW) - Viewing table structure (DESCRIBE) </usecase> <when_not_to_use> - Data changes (INSERT, UPDATE, DELETE) → use writeQuery (not available in read-only mode) - Query performance analysis → use explainQuery - Discovering tables or columns → use listTables (pass detailed=true for column-level metadata) - Switching database context (USE is rejected) → pass the `database` argument </when_not_to_use> <examples> ✓ "SELECT * FROM users WHERE status = 'active'" ✓ "SELECT COUNT(*) FROM orders GROUP BY region" ✓ "SHOW TABLES" or "DESCRIBE users" ✗ "INSERT INTO users ..." → use writeQuery (not available in read-only mode) ✗ "EXPLAIN SELECT ..." → use explainQuery for structured analysis </examples> <what_it_returns> A JSON array of row objects, each keyed by column name. Long string values are cut and end in `…[truncated, N chars total]`; read the rest with `SUBSTRING`/`SUBSTR`. Rows past the response size cap are dropped: a `SELECT` page ends early and `nextCursor` resumes at the first row left out, while other statements report the count in `rowsOmitted`. When either happens the response carries `truncated: true` and a `hint`. </what_it_returns> <pagination> `SELECT` results are paginated. Pass the prior response's `nextCursor` as `cursor` to fetch the next page. Order by a unique key so pages neither skip nor repeat rows. `SHOW`, `DESCRIBE`, and `EXPLAIN` return a single page and ignore `cursor`. </pagination> <timeout> Each call stops at the configured query timeout. On a timeout, check the plan with explainQuery before retrying: filter on indexed columns, or limit inner result sets before joining or aggregating. For a query known to be slow, pass `timeout` (seconds, at least 1) to allow more time. This only helps if the server allows a higher maximum, which is often the same as the default; a value above it is rejected with an error naming the maximum. </timeout>
- CurrentExecute a read-only SQL query. Allowed statements: SELECT, SHOW, DESCRIBE, EXPLAIN. <usecase> Use when: - Querying data from tables (SELECT with WHERE, JOIN, GROUP BY, etc.) - Aggregations: COUNT, SUM, AVG, GROUP BY, HAVING - Listing server variables or status (SHOW) - Viewing table structure (DESCRIBE) </usecase> <when_not_to_use> - Data changes (INSERT, UPDATE, DELETE) → use writeQuery (not available in read-only mode) - Query performance analysis → use explainQuery - Discovering tables or columns → use listTables (pass detailed=true for column-level metadata) - Switching database context (USE is rejected) → pass the `database` argument </when_not_to_use> <examples> ✓ "SELECT * FROM users WHERE status = 'active'" ✓ "SELECT COUNT(*) FROM orders GROUP BY region" ✓ "SHOW TABLES" or "DESCRIBE users" ✗ "INSERT INTO users ..." → use writeQuery (not available in read-only mode) ✗ "EXPLAIN SELECT ..." → use explainQuery for structured analysis </examples> <what_it_returns> A JSON array of row objects, each keyed by column name. Long string values are cut and end in `…[truncated, N chars total]`; read the rest with `SUBSTRING`/`SUBSTR`. Rows past the response size cap are dropped: a `SELECT` page ends early and `nextCursor` resumes at the first row left out, while other statements report the count in `rowsOmitted`. When either happens the response carries `truncated: true` and a `hint`. </what_it_returns> <pagination> `SELECT` results are paginated. Pass the prior response's `nextCursor` as `cursor` to fetch the next page. Order by a unique key so pages neither skip nor repeat rows. Pages stay within the statement's own `LIMIT` and `OFFSET`. Write a row limit as a literal `LIMIT n`: other forms (`FETCH FIRST`, expressions) make every page read the whole result. `SHOW`, `DESCRIBE`, and `EXPLAIN` return a single page and ignore `cursor`. </pagination> <timeout> Each call stops at the configured query timeout. On a timeout, check the plan with explainQuery before retrying: filter on indexed columns, or limit inner result sets before joining or aggregating. For a query known to be slow, pass `timeout` (seconds, at least 1) to allow more time. This only helps if the server allows a higher maximum, which is often the same as the default; a value above it is rejected with an error naming the maximum. </timeout>
Input schema
Input schema unchanged.
5 unchanged entries
(schema root)cursordatabasequerytimeout
Output schema
Output schema unchanged.
7 unchanged entries
(schema root)hintnextCursorrowsrows › [items]rowsOmittedtruncated
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
No tools match these filters.
6 tools with no recorded change
listDatabaseslistFunctionslistProcedureslistTableslistTriggerslistViews
Evidence and provenance
- Static findings
- PASS from Modelara’s automated analysis of the two declared interfaces. A policy outcome, not a security rating or a runtime test.
- Human review
- Automated static analysis. No reviewer decision is recorded for this comparison.
- Published evidence
- Part of Valyd’s published data generation listed in valyd-data-source.json. Published records are not rewritten.
Show provenance and exact files
- Comparison
haymon-dbmcp/0.18.1~0.19.0The published comparison identifier.- Analyzer
modelara v0.1.8Policy version not recorded.Analyzed Nov 16, 2026, 11:35 PM UTC.- Distribution
npm- Previous release
@haymon-ai/dbmcp@0.18.18 tools · published by the registry Nov 11, 2026, 5:35 PM UTCArtifact integritysha512-KKG0Umn1Odvh0hsyU6WOIrc1A44sP4nnesv4ky01wxZARXfEJwFud1Zy4vlOsBkR93/AMqLEpSB0Xt2aTfYphw==Interface fingerprintsha256:ae96c237c8532ff448f4aad9f6de5b02b43c294a3b91eaa67ec029771b4a6803Exact interface snapshot (JSON)- Current release
@haymon-ai/dbmcp@0.19.08 tools · published by the registry Nov 16, 2026, 10:50 AM UTCArtifact integritysha512-AElllCdpu2S3IAIi8eubbNMMov3+6XgNrHYwy3aEOpIKfMEl/HaTL3BXPux1tFxyWILon/wNf/Ceo1R5ciAX1Q==Interface fingerprintsha256:c53fd64b4e499be7de972021e75798f2274670aa00d7442b62d3e3cc72eece0dExact interface snapshot (JSON)- Comparison record
- Exact comparison record (JSON)
The integrity value or digest identifies the exact artifact that was inspected; it does not show that the package is safe. The interface fingerprint identifies the declared tools and schemas Modelara recorded for that release.
MODELARA ANALYSIS OUTPUT
Interface findings
Informational
2 findingsexplainQueryINFOChangedreadQueryINFOChanged
What do these results mean?
- PASS
- No policy-significant interface change detected.
- REVIEW
- Interface changes require inspection.
- FAIL
- A policy-significant change was detected.
- INVALID
- The comparison could not be evaluated reliably.