Skip to main content
Glama
Sign In

QuintaDB

by com.quintadb
OverviewDiscussionsAdmin

get_reports

Read-onlyIdempotent

The project's reports (saved views of a table: filters, grouping, totals). Without entity_id: EVERY report of every table, each with its id and the table it belongs to — use this when the person names a report and not its table; never guess the table from the report's name. With entity_id: that one table's reports.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "app_id": "<app_id>"
    },
    "name": "get_reports"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idYesProject ID (from list_projects)
entity_idNoA table's id. Leave it out to list the reports of the whole project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / entity_id / description
      Previous value: -"Form ID (from list_forms or describe_project)"New value: +"A table's id. Leave it out to list the reports of the whole project."
    • changedInput schema / required
      Previous value: -[
-  "app_id",
-  "entity_id"
-]New value: +[
+  "app_id"
+]
  2. First observed

TDQS

A4.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds useful scoping behavior — the cross-table listing that includes each report's id and owning table — but does not address ordering, pagination, or completeness of the listing. Adequate but not rich beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the definition of a report, then splits the two modes cleanly. Every clause earns its place — the parenthetical definition and the 'never guess the table' warning both prevent agent errors.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Two-param read tool with full schema coverage and safety annotations. The description covers the one non-obvious behavior (cross-table listing with owning table) and the routing decision. No output schema exists, but the return shape is described enough to use the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and already documents both params. The description adds semantic meaning beyond the schema: entity_id acts as a scope switch, and the no-entity_id mode returns each report with its id and owning table. That goes beyond the schema's plain restatement.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (get) and resource (reports, defined as saved views of a table with filters/grouping/totals), and clearly distinguishes the two invocation modes. An agent can tell it apart from create_report, update_report, delete_report, and get_report_data without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to omit entity_id (person names a report, not its table; never guess the table from the report's name) and when to supply it (one table's reports). This is unusually strong routing guidance that directly prevents a common agent error.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All QuintaDB toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources