Skip to main content
Glama
Sign In
Coletum MCP Server

Coletum MCP Server

Official
by geo-sapiens
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

listar_formularios

Read-only

Retrieve account forms with IDs, names, statuses, categories, and versions. Use the returned form IDs as the starting point for all other Coletum MCP Server tools.

Instructions

Lista os formulários da conta: id, nome, status, categoria e versão.

Custo: 1 chamada por página, cerca de 200 bytes por formulário. Use tamanho_pagina alto (até 500) para ver tudo em 1 chamada. É o ponto de partida: o id daqui entra em todas as outras ferramentas.

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

Input Schema

NameRequiredDescriptionDefault
nomeNoParte do nome do formulário (busca parcial, sem diferenciar maiúsculas).
paginaNoPágina, começando em 1.
statusNoenabled (habilitados) ou disabled (desabilitados). Vazio traz todos.
tamanho_paginaNoFormulários por página (máximo 500).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true). The description adds genuinely useful behavior beyond that: cost of ~1 call per page and ~200 bytes per form, plus which fields come back. It omits pagination terminator/ordering details but covers the operational cost model well.

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 lines, front-loaded with purpose, then cost, then routing advice. Every sentence earns its place; only the byte-per-form estimate is mildly incidental.

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?

With no output schema, the description correctly compensates by listing the returned fields and describing the cost/volume profile of the call. What remains unspecified (ordering, total count, pagination end condition) is minor for a read-only list tool.

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?

Schema description coverage is 100%, so all four parameters (nome, pagina, status, tamanho_pagina) are already documented in the schema. The description only adds a strategic hint about tamanho_pagina; it contributes no semantic detail beyond what the schema provides, so the baseline of 3 applies.

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+resource ('Lista os formulários da conta') and enumerates the returned fields (id, nome, status, categoria, versão). It also positions itself against siblings by declaring it is the entry point whose id feeds every other tool.

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?

Gives explicit usage context: it is the starting point and the id obtained here is consumed by all sibling tools, plus a concrete tip to raise tamanho_pagina to 500 to avoid paginating. It does not state when NOT to use it or name a filtering alternative.

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

Deploy Server

Other Tools