Skip to main content
Glama

Rede Celcoin MCP

by io.github.mcp-dir

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
NameRequiredDescriptionDefault
limitNo
queryNo
actionNosearch
mcp_idNo
messageNo
tool_idNo
argumentsNo{}
immediateNo
tier_slugNo
prompt_bodyNo
prompt_slugNo
prompt_toolNo
prompt_varsNo{}
conversationNo[]
prompt_titleNo
request_nameNo
cancel_reasonNo
cancel_commentNo
prompt_targetsNo
report_contextNo
prompt_categoryNo
request_detailsNo
prompt_descriptionNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Added
  6. Removed
  7. Added
  8. Removed
  9. Added
  10. Removed
  11. Added
  12. Removed
  13. Changed9 schema fields changed
    • 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"
+}
  14. Changed1 schema field changed
    • 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"
+]
  15. Changed2 schema fields changed
    • 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"
+}
  16. Added
  17. Removed
  18. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations are minimal (readOnlyHint false, openWorldHint true, etc.), so the description carries the burden. It discloses many behaviors: invoke works without installation, returns connect/checkout links when needed, install makes permanent, writes require owner/admin, and prompt links open without login. These go beyond annotations and are not contradicted by them.

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 the tool is complex (multi-action marketplace + prompt library). It is front-loaded with the main purpose and uses clear flow markers ('Core flow', 'KEY'). The occasional verbal clutter (e.g., 'pontualmente') and dense first sentence slightly reduce conciseness, but all content earns its place.

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 is comprehensive given the tool's complexity: it covers all major action categories, edge cases (auth, payments), permission requirements, and the prompt library. Without an output schema, it gives partial output descriptions (e.g., 'returns a connect link', 'returns a shareable link') but not for every action. Overall, it is robust enough for an agent to use correctly.

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 meaningfully explains the `action` enum and key parameters like `tool_id` and `query` through the core flow. However, many parameters (e.g., `immediate`, `tier_slug`, `prompt_vars`, `cancel_reason`) are not explicitly described, though some are inferable from defaults/enums. It substantially compensates but not fully exhaustively.

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 — the in-platform catalog of every MCP/tool, AND the way to run them,' and outlines its core functions (search, describe, invoke) and prompt library. It distinguishes this from sibling tools by its broad catalog/execution role versus the specific openfinance 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?

The description gives explicit guidance on when to use each action ('Core flow: action=search → describe → invoke'), contrasts invoke versus install ('Use install only to make an MCP PERMANENT... prefer invoke for a single/occasional use'), and lists alternatives like request_mcp for new MCPs and prompt library for prompts. It also notes permission requirements for writes.

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

All Rede Celcoin MCP toolsInspect
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.9/5.0
Disambiguation3/5

Most openfinance_* tools target distinct resources and actions, but several overlap in purpose: list_transactions vs list_transactions_by_item, get_credit_card_bill vs list_credit_card_bills, and multiple connection/status tools expose reconnect URLs. The long descriptions help, but the boundaries are not always immediately obvious.

Naming Consistency4/5

The openfinance_* tools follow a consistent list_/get_ verb_noun pattern and share a clear prefix. The smaller platform cluster is less consistent — marketplace, connect, authenticate, show_version, toolkit_info — mixing nouns, bare verbs, and snake_case, but it is a minor deviation overall.

Tool Count3/5

At 25 tools, this sits at the heavy end of acceptable. The Open Finance surface is broad enough to justify many of them, but there is redundancy (e.g. list_transactions_by_item largely wraps list_transactions plus account resolution) and a separate platform-management cluster that makes the set feel sprawling.

Completeness4/5

The Open Finance domain is well covered: connection lifecycle, accounts, balances, transactions, credit-card bills, loans, investments, categories, and provider status are all present, and data flows connect properly between tools. Minor gaps exist, such as no single-transaction fetch or dedicated prompt-management tools, but the marketplace tool fills those roles.

Resources