Certidão TJ (Cível, Criminal e Fiscal)

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

Behavior5/5

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

Discloses that invoke runs one-off without installing, returns connect links for auth needs, checkout links for empty wallet, and that writes require workspace owner/admin. This goes beyond the sparse annotations (readOnlyHint=false, openWorldHint=true) by clarifying side effects and permissions.

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 information-dense, organized around the core action flow, install vs invoke distinction, and prompt library. It is front-loaded with the essential purpose and each sentence adds useful guidance, though a more paragraph-structured layout would improve readability.

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

Completeness5/5

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

Covers the full action surface: search, describe, invoke, install, list_tools, billing, bug reports, prompt publishing, and permissions. Despite no output schema, it explains expected result types (connect link, checkout link, slug link) and auth requirements, making it near-complete for a 23-parameter multi-action tool.

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 action semantics and key parameters (mcp_id, tool_id, arguments) through the core flow. It also contextualizes billing and prompt params via subscribe/cancel and publish_prompt, though not all 23 params are individually detailed.

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?

Clearly states it is the official mcp.ai marketplace — the in-platform catalog of every MCP/tool and the way to run them. Also covers capability requests and prompt library, distinguishing it from siblings like authenticate, connect, and 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?

Explicitly instructs to prefer invoke for single/occasional use, install only for permanent addition, and list_tools for currently callable tools. Also explains when to use request_mcp, search_prompts, and report_bug, giving clear decision guidance.

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

All Certidão TJ (Cível, Criminal e Fiscal) 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

Disambiguation3/5

The tools serve mostly distinct purposes, but the marketplace tool is a broad catch-all that overlaps with the domain tool (can search for CPF-related MCPs) and includes many sub-actions. Additionally, connect and toolkit_info both report connection status, creating some ambiguity. Detailed descriptions help, but selection risk remains.

Naming Consistency2/5

Tool names are all lowercase snake_case, but the pattern is inconsistent: some are single verbs (authenticate, connect), some are nouns (marketplace), and only a few follow a verb_noun style. The domain-specific tool uses a different convention (tj_certidao_consultar). This mixed naming makes it hard to predict tool behavior from names alone.

Tool Count3/5

The 7-tool count is within a reasonable range, but the server is named for a specific domain (TJ certificates) yet devotes 6 of 7 tools to generic platform management. This creates a scope mismatch where the domain surface is a single tool and the platform tools feel out of place, though the number itself is not excessive.

Completeness2/5

The only domain tool covers the core consult operation, but there are no other certidão-related tools (e.g., list past requests, check status, or generate a specific variant). The platform tools do not address the domain's completeness, leaving significant gaps for typical certificate workflows.

marketplace

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources