Skip to main content
Glama

tiss_sadt_catalog

Read-only

Retorna o catálogo SP/SADT. Quando usar: para conhecer campos e domínios. Quando não usar: para preencher uma guia sem dados.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tiss_sadt_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered and the description only needs to add shape. It adds that the payload is a catalog of fields and domains, but says nothing about catalog size or how to navigate it — meaningful for an agent that will load this into context.

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

Conciseness4/5

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

Three short clauses, front-loaded with the return value before the usage rules — nothing redundant. The final clause is terse to the point of being opaque, which slightly undercuts the otherwise clean structure.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and with zero parameters the description carries little burden. Still, the "quando não usar" clause is vague and never says what to use instead, leaving a real routing gap against the many tiss_* siblings.

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?

The tool takes zero parameters and the description correctly does not invent any, so there is no parameter meaning to add. The baseline for a parameterless tool applies; the description's mention of fields and domains implicitly frames what the returned entries look like.

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?

"Retorna o catálogo SP/SADT" gives a clear verb (returns) plus a specific resource (the SP/SADT catalog), and the follow-up sentence narrows it to field/domain knowledge. It does not differentiate itself from related metadata siblings such as tiss_dominio or tiss_referencia, so an agent cannot tell from the text alone which catalog tool to pick.

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

Usage Guidelines4/5

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

Explicit "Quando usar" / "Quando não usar" structure gives both a positive trigger (learning fields and domains) and an exclusion. However, the exclusion ("para preencher uma guia sem dados") is a misuse warning rather than a named alternative, so the agent is not routed to the tool it should use instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.