Conta Simples

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.

Changed9 schema fields changedAug 10, 2026

changedInput schema / properties / action / enum

Previous value: -[
-  "search",
-  "describe",
-  "install",
-  "uninstall",
-  "subscribe",
-  "cancel",
-  "resume",
-  "report_bug",
-  "request_mcp",
-  "list_tools",
-  "invoke"
-]New value: +[
+  "search",
+  "describe",
+  "install",
+  "uninstall",
+  "subscribe",
+  "cancel",
+  "resume",
+  "report_bug",
+  "request_mcp",
+  "list_tools",
+  "invoke",
+  "search_prompts",
+  "get_prompt",
+  "publish_prompt"
+]

addedInput schema / properties / prompt_body

Added value: +{
+  "default": "",
+  "type": "string"
+}

addedInput schema / properties / prompt_category

Added value: +{
+  "default": "",
+  "type": "string"
+}

addedInput schema / properties / prompt_description

Added value: +{
+  "default": "",
+  "type": "string"
+}

addedInput schema / properties / prompt_slug

Added value: +{
+  "default": "",
+  "type": "string"
+}

addedInput schema / properties / prompt_targets

Added value: +{
+  "default": [],
+  "items": {
+    "enum": [
+      "claude",
+      "chatgpt",
+      "cursor",
+      "lovable"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / prompt_title

Added value: +{
+  "default": "",
+  "type": "string"
+}

addedInput schema / properties / prompt_tool

Added value: +{
+  "default": "",
+  "type": "string"
+}

addedInput schema / properties / prompt_vars

Added value: +{
+  "default": "{}",
+  "type": "string"
+}

Changed1 schema field changedJul 29, 2026

changedInput schema / properties / action / enum

Previous value: -[
-  "search",
-  "describe",
-  "install",
-  "uninstall",
-  "subscribe",
-  "cancel",
-  "report_bug",
-  "request_mcp",
-  "list_tools",
-  "invoke"
-]New value: +[
+  "search",
+  "describe",
+  "install",
+  "uninstall",
+  "subscribe",
+  "cancel",
+  "resume",
+  "report_bug",
+  "request_mcp",
+  "list_tools",
+  "invoke"
+]

Changed2 schema fields changedJul 10, 2026

addedInput schema / properties / cancel_comment

Added value: +{
+  "default": "",
+  "type": "string"
+}

addedInput schema / properties / cancel_reason

Added value: +{
+  "enum": [
+    "too_expensive",
+    "missing_features",
+    "switched_service",
+    "unused",
+    "customer_service",
+    "too_complex",
+    "low_quality",
+    "other"
+  ],
+  "type": "string"
+}

First observedJun 11, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description richly discloses behaviors beyond annotations: invoke runs one-off without installing the MCP, returns connect links for credentials and checkout links for paid tools with empty wallets, and that search/describe flag installed states. It also explains the distinction between one-off invoke and permanent install, and covers auth requirements for writes.

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, with each sentence adding a distinct behavioral or usage detail. It is front-loaded with a high-level purpose, then flows through the search-describe-invoke workflow, and covers the prompt library. While concise for the tool's complexity, it could be slightly more structured with separation between the MCP flow, billing, and prompt library sections.

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 tool's complexity (23 parameters, 14 actions) and no output schema, the description covers the essential workflows, auth, and billing semantics, the prompt library, and key constraints like invoke's one-off behavior. Minor gaps include the 'resume' action, the 'immediate' parameter, and precise handling of request_mcp details, but overall it provides sufficient context for an agent to select and invoke the tool correctly for most use cases.

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 schema description coverage at 0%, the description is the primary source for parameter meaning. It explains the action parameter's enum values through the core workflow (search, describe, invoke, install, subscribe, cancel, list_tools, report_bug, request_mcp, search_prompts, get_prompt, publish_prompt), and implicitly references mcp_id, tool_id, arguments, prompt fields, and tier_slug. However, it does not dissolve every parameter (e.g., 'immediate', 'conversation') or specify the JSON format for arguments or prompt_vars, leaving some guidance gaps.

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 and execution gateway, with a specific core flow (search → describe → invoke). It explicitly lists the categories of capability requests it covers ('find an MCP that does X', 'consulta um CPF', 'is there a tool for Y'), distinguishing it from the sibling contasimples_* tools and other utility tools.

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 when-to-use vs alternatives: 'prefer invoke for a single/occasional use' vs 'use install only to make an MCP PERMANENT', and notes 'list_tools lists what is callable right now' and 'request_mcp asks us to build a NEW MCP when nothing fits.' Also states that writes require workspace owner/admin, guiding the agent on permission prerequisites.

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

All Conta Simples 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.5/5.0

Disambiguation4/5

Almost all tools have clear purposes, especially with the contasimples_ prefix. Some overlap between statement and summary, but descriptions differentiate well. The general tools (marketplace, report_bug, etc.) are completely different from the financial ones, which reduces potential confusion.

Naming Consistency3/5

The domain tools follow a consistent verb_noun pattern (e.g., contasimples_card_write_block). However, the inclusion of general tools like authenticate, connect, marketplace breaks the pattern. This inconsistency lowers the score.

Tool Count4/5

With 24 tools covering authentication, financial operations, and platform utilities, the number is reasonable for a moderately complex MCP server. It doesn't feel excessive or too thin.

Completeness3/5

The toolset covers key financial operations (balance, bills, cards, statements, summary) and some mutations (block/unblock, create invite, delete user). However, missing CRUD for several entities (e.g., no update user, no create card, no delete invite) leaves gaps. The presence of platform utilities adds breadth but not depth.

marketplace

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources