Similaridade de Identidade (Argentina)

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?

Beyond annotations, the description discloses key behaviors: invoke works even when the MCP is not installed, returns connect links for credentials and checkout links for payment, requires workspace owner/admin for writes, and flags installed_in_toolkit vs installed_in_workspace. These details go far beyond the basic readOnly/destructive hints.

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 front-loaded with the core purpose and flow. While it is dense and covers a lot, each sentence adds meaningful information about actions or behaviors; no significant redundancy. The structure is a single large paragraph, which could be improved with bullets, but it remains efficient for 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?

The description covers the main flows (search/describe/invoke, install vs invoke, prompt library), auth requirements, billing links, and permissions. It omits details on some actions like 'resume' and parameters like 'immediate' or 'tier_slug', but the core decision-making context is adequately provided for an agent to use the 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 23 parameters and 0% schema coverage, the description compensates by explaining the action enum values, the relationship between mcp_id and tool_id, and the prompt_vars for get_prompt. However, it leaves many parameters (limit, query, tier_slug, cancel_reason, etc.) undocumented, relying on inference from the action descriptions.

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 identifies the tool as the official mcp.ai marketplace, serving as both a catalog and runtime for MCPs. It enumerates specific functions (search, describe, invoke, install, prompt library) and differentiates itself from sibling tools by being the only marketplace and prompt library among them.

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 guidance on when to use which action: 'prefer invoke for a single/occasional use' vs 'use install only to make an MCP PERMANENT', and 'request_mcp asks us to build a NEW MCP when nothing fits'. It also explains the flow from search to describe to invoke, making it clear how to navigate the tool.

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

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

Most tools have clear purposes, but 'connect' and 'toolkit_info' both report connection status, and 'marketplace' subsumes listing tools which overlaps with 'toolkit_info'. These overlapping responsibilities could cause an agent to select the wrong tool.

Naming Consistency2/5

Tool names are inconsistent: some are bare verbs (connect, authenticate), some use verb_noun (report_bug, show_version), some are noun phrases (toolkit_info, marketplace), and one is a long Portuguese phrase (similaridade_ar_consultar). No coherent pattern.

Tool Count4/5

7 tools is a reasonable count, but the set mixes generic platform management (authenticate, connect, marketplace, etc.) with a single domain-specific query tool, which makes it feel slightly over-scoped for the apparent purpose of identity similarity.

Completeness4/5

The platform side covers auth, status, marketplace search/invoke, bug reporting, version info, and toolkit state, so it is fairly complete. The domain side has only a consult operation, but that matches the simple query nature of the service, so no major gaps.

marketplace

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources