Servidores Federais Completa (Transparência)

marketplace

The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/ link that opens without login.

Input Schema

TableJSON Schema

Name	Required	Default
`limit`	No
`query`	No
`action`	No	search
`mcp_id`	No
`message`	No
`tool_id`	No
`arguments`	No	{}
`immediate`	No
`tier_slug`	No
`prompt_body`	No
`prompt_slug`	No
`prompt_tool`	No
`prompt_vars`	No	{}
`conversation`	No	[]
`prompt_title`	No
`request_name`	No
`cancel_reason`	No
`cancel_comment`	No
`prompt_targets`	No
`report_context`	No
`prompt_category`	No
`request_details`	No
`prompt_description`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedAug 17, 2026

TDQS

A4.3/5.0

Behavior5/5

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

It discloses key behaviors beyond annotations: invoke runs uninstalled MCPs without bloating the toolkit, credential and payment failures return connect/checkout links, and search/describe surface installation state. It also explains that writes require admin, all of which is valuable context not available from annotations alone.

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?

The description is front-loaded with the tool's purpose and core flow, and nearly every sentence adds relevant information for a complex 14-action tool. However, it is a long dense paragraph that could benefit from bullet points or section breaks, and it mixes languages ('pontualmente', 'consult um CPF').

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?

For its complexity, the description covers the main flows, auth requirements, one-off vs permanent installation, payment/connect edge cases, and the separate prompt library. It does not cover output/return formats or detailed error handling, but the absence of an output schema makes this an acceptable gap.

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 coverage is 0%, so the description must compensate for 23 parameters. It adds meaning for the `action` values and the `tool_id`/invoke relationship, but many parameters (`limit`, `immediate`, `tier_slug`, `conversation`, prompt payload fields) are never explained, leaving significant gaps for correct invocation.

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 identifies the tool as the mcp.ai marketplace: a catalog of MCP/tool and the mechanism to run them. It names the main actions and distinguishes the core flow (search → describe → invoke), but does not explicitly contrast the marketplace with sibling tools like `authenticate` or `toolkit_info`.

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?

The description gives explicit, actionable guidance: use `search` to discover, `describe` to choose a tool_id, `invoke` to run one-off, and `install` only for permanent toolkit additions. It also states that writes require workspace owner/admin, and clarifies when to use `request_mcp` vs `report_bug`.

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

All Servidores Federais Completa (Transparência) tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0

Disambiguation2/5

Several tools have overlapping responsibilities: 'connect' and 'toolkit_info' both return connection/status info, 'authenticate' handles session/auth concerns, and 'marketplace' bundles numerous actions (including install, subscribe, cancel, report_bug) that duplicate capabilities of 'report_bug' and other tools. Agents would struggle to choose the right tool without examining internal action parameters.

Naming Consistency2/5

Tool names follow no consistent pattern: some are bare verbs ('authenticate', 'connect'), some are verb_noun ('report_bug', 'show_version'), one is a noun ('marketplace'), and the domain-specific tool uses a long Portuguese composite ('transparencia_servidores_completa_consultar'). The mix of English platform verbs and a Portuguese domain name adds inconsistency.

Tool Count3/5

Seven tools is within an acceptable range, but the 'marketplace' tool is a monolithic catch-all containing search, describe, invoke, install, list, subscribe, cancel, report_bug, request_mcp, and prompt management, effectively representing 12+ operations under one tool. This makes the actual surface area much larger than the count suggests, though the number itself is reasonable.

Completeness2/5

The server's stated purpose is federal employee transparency, but only a single CPF query tool is provided, with no listing, filtering, or batch operations. The platform admin tools (authenticate, connect, marketplace, etc.) are comprehensive, but they don't cover the transparency domain, which appears to be the server's primary focus. Many common transparency needs remain unsupported.

marketplace

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources