Certidão de Débitos PF

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.7/5.0

Behavior5/5

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

The description discloses key behaviors beyond annotations: invoke runs one-off without installing, returns connect/checkout links, and requires owner/admin for writes. It explains the distinction between installed_in_toolkit vs installed_in_workspace and details the prompt library behavior. This adds substantial context beyond the sparse annotations.

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 long but structured and front-loaded with the core purpose. Each sentence adds value, explaining flow, exceptions, and the prompt library. While dense, it earns its length given the tool's complexity.

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 the high complexity (14 actions, 23 params, no output schema), the description is remarkably complete: it covers the core flow, credential/payment edge cases, auth requirements, and the prompt library. It does not exhaustively describe every return value, but it covers most user-facing outcomes.

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?

With 0% schema description coverage, the description compensates by explaining the semantics of core parameters like action, mcp_id, tool_id, and arguments through the described flow. It also discusses prompt-related parameters implicitly. However, many parameters (limit, query, immediate, tier_slug, cancel_reason, etc.) remain unexplained, so it doesn't fully cover all 23 parameters.

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?

The description clearly states the tool is the official mcp.ai marketplace: the in-platform catalog of every MCP/tool and the way to run them. It uses specific action verbs like 'search', 'describe', 'invoke', and 'install', and differentiates from sibling tools by covering the entire marketplace lifecycle.

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?

Provides explicit guidance on when to use each action: 'prefer invoke for a single/occasional use', 'Use install only to make an MCP PERMANENT', and explains the core flow with action=search → describe → invoke. It also specifies when credentials or payment are needed and that writes require workspace owner/admin.

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

All Certidão de Débitos PF 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

A3.7/5.0

Disambiguation4/5

Each tool has a clear, distinct purpose, and the descriptions prevent direct overlap. The only slight ambiguity is between authenticate and connect, but both are adequately differentiated. However, the mix of generic platform tools with a single domain tool may confuse an agent about which to use for certificate tasks.

Naming Consistency2/5

Tool names are highly inconsistent: some are verbs (authenticate, connect), some are nouns (marketplace, toolkit_info), one is a long Portuguese snake_case (certidao_debitos_pf_consultar), and others mix verb_noun patterns (report_bug, show_version). The language mixing and lack of a uniform convention make the naming chaotic.

Tool Count3/5

Seven tools is within a reasonable range, but the server's name suggests a focused domain service, and only one tool actually serves that domain. The other six are generic platform utilities, making the count feel bloated for the apparent purpose and creating a scope mismatch.

Completeness2/5

For the stated domain of certidão de débitos, only a single consult operation is provided, with no supporting tools for history, downloads, or related management. The platform utilities do not address domain-specific gaps, leaving the coverage severely incomplete for the server's implied purpose.

marketplace

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources