Skip to main content
Glama
Sign In

QuintaDB

by com.quintadb
OverviewDiscussionsAdmin

list_saved_views

Read-onlyIdempotent

List of a table's saved filters/views (SearchResult). Lets the agent learn which views already exist.

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": "list_saved_views"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idYesProject ID (from list_projects)
entity_idNoOptional — filter by form

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / entity_id / description
      Previous value: -"Опційно — фільтр по формі"New value: +"Optional — filter by form"
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

The description adds semantic context by stating it helps the agent 'learn which views already exist.' This explains the operational utility of the tool, which is useful even when strong hints are provided via annotations like readOnlyHint: true.

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

Conciseness3/5

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

The description is a concise two-sentence paragraph. However, the first sentence uses parenthetical framing '(SearchResult)' that is slightly redundant given the function name 'list_saved_views'.

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

Completeness4/5

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

Given that all parameters are covered by the schema (100% coverage) and strong safety annotations are present, the description is functionally complete in defining the tool's scope.

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

Parameters3/5

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

Since schema description coverage is 100%, the schema defines all parameters. The description provides no additional insight into the semantic meaning of 'app_id' or 'entity_id' beyond what the structured schema already provides.

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

Purpose4/5

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

The description clearly states the resource being managed—'a table's saved filters/views'—and the action being performed ('List'). While the name is self-explanatory, the description confirms it returns a SearchResult.

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

Usage Guidelines2/5

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

The description offers no guidance on when to use this tool versus others (e.g., checking if a view exists before creating one). It merely states its purpose without providing necessary workflow context.

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