Conselho Regional de Odontologia RO: Cadastro, consulta em fonte oficial. Hospedado pela plataforma, sem credenciais da plataforma, pague por consulta com crédito pré-pago. Consulta informação de fontes e órgãos oficiais brasileiros (a mesma disponível ao cidadão), não é dado sigiloso. O cliente é o controlador dos dados e responde pela finalidade legítima (LGPD).
| Name | Required | Description | Default |
|---|---|---|---|
| inscricao | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description goes beyond the readOnlyHint annotation by stating that the data is official, not confidential, and that the client is responsible for legitimate purpose under LGPD. This adds meaningful behavioral context about data sensitivity and legal obligations, though it omits details like failure modes or rate limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is reasonably concise and includes essential information about the data source, payment method, and legal disclaimer. It is not overly verbose, though it could be slightly tightened without losing clarity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool lacks an output schema, and the description does not specify what data will be returned after a query. It also does not mention error handling or response format. Given the simplicity of a query tool, this omission is noticeable but not critical.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The only parameter 'inscricao' is not explained in the description. While the name hints at a registration number, no format, required pattern, or example is provided. The description adds no value to understanding the parameter beyond its literal name.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly specifies the action (consulta) and the resource (Cadastro from Conselho Regional de Odontologia RO), distinguishing it from generic sibling tools like authenticate or show_version. The purpose is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides some usage context: hosted on the platform, no platform credentials required, and payment via prepaid credit. However, it does not explicitly state when to use this tool versus other alternatives, nor provide conditions for non-use. The payment and credential info is helpful but incomplete as a guideline.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.