SEFAZ PE DEC: Caixa Postal

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 19, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Beyond annotations (readOnlyHint false, openWorldHint true), the description discloses that writes require owner/admin, invoke works even if MCP not installed, and describes return behavior for credential/payment cases (connect link, checkout link). This adds valuable non-obvious behavioral details.

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

Conciseness2/5

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

The description is overly long and rambling, mixing languages (Portuguese) and repeating concepts (e.g., credential/payment details are stated twice). It lacks a clear hierarchical structure, making it harder to parse despite its length.

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

Completeness2/5

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

While the description covers high-level flows (invoke, install, etc.), it omits details for many parameters and actions, especially the prompt-related ones (search_prompts, get_prompt, publish_prompt). It does not address output schemas or expected return structures, leaving the tool context incomplete for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 23 parameters with no descriptions, and the description does not explain any of them (e.g., prompt_body, tool_id, cancel_reason). It mentions 'id + params' in the describe flow but fails to clarify what each input parameter means or how they map to actions, leaving parameter semantics largely unexplained.

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 explicitly states the tool is the official mcp.ai marketplace, the in-platform catalog of MCPs/tools, and explains the core flow (search, describe, invoke). It is a specific verb (marketplace) with resource (MCPs and prompts) and distinguishes from siblings by covering both tools and prompts.

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?

The description provides conditional guidance: 'Use install only to make an MCP PERMANENT... prefer invoke for a single/occasional use.' It also explains when invoke works without installation and notes permission requirements for writes, which helps decide when to use this tool versus alternatives.

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

All SEFAZ PE DEC: Caixa Postal 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.

marketplace

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources