Skip to main content
Glama

Unicred 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. Added
  14. Removed
  15. 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"
+}
  16. 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"
+]
  17. 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"
+}
  18. Added
  19. Removed
  20. First observed

TDQS

A4.5/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, returns connect/checkout links for auth/payment, and writes require workspace owner/admin. It also notes that search/describe flag install states. These details add significant transparency beyond the bare annotations.

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, then layers in key behavioral nuances and the prompt library. Each section adds necessary information for a complex 14-action tool, though it could be tightened with bullet points or shorter paragraphs.

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 breadth (14 actions, 23 params, no output schema), the description covers the main flows, auth/payment behaviors, install vs invoke, and prompt library. It does not detail return structures for actions like search or list_tools, and some params/edge cases remain unexplained, leaving residual gaps.

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

Parameters3/5

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

With 0% schema coverage, the description partially compensates by explaining the roles of key parameters (action, tool_id, prompt_slug/vars via the prompt flow). However, it leaves many of the 23 parameters undefined (e.g., limit, query, immediate, tier_slug, report_context, request_details), so the agent still lacks explicit semantics for the full parameter set.

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 identifies the tool as the mcp.ai marketplace — the in-platform catalog and runner for MCPs/tools, with a clear core flow (search → describe → invoke). It distinguishes itself from sibling tools by detailing its all-encompassing role and the prompt library, making its purpose unambiguous.

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 guidance: 'prefer invoke for a single/occasional use' vs 'Use install only to make an MCP PERMANENT', and explains the purpose of each action (search/describe/invoke, subscribe/cancel, report_bug, request_mcp, prompt library). It also states the permission requirement for writes and specifies when invoke returns connect/checkout links, giving clear decision criteria.

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

All Unicred 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
Disambiguation4/5

The openfinance_* tools are clearly separated by resource and action—accounts, transactions, bills, loans, investments, and connection status—so an agent can usually tell them apart. A few pairs remain confusable, notably openfinance_list_transactions vs openfinance_list_transactions_by_item and the monolithic marketplace tool overlapping with report_bug, but the detailed descriptions largely resolve the boundaries.

Naming Consistency4/5

The openfinance_* subset follows a consistent snake_case verb_noun convention (list_accounts, get_item_status, update_transaction_category), and non-openfinance tools like report_bug and show_version fit the same style. The pattern breaks with bare verbs/nouns such as connect, authenticate, marketplace, and toolkit_info, but the domain prefix makes the majority predictable.

Tool Count3/5

25 tools sits at the top of the heavy-but-manageable range, and the Open Finance resource pairs plus platform/marketplace tools each earn some place. The count feels slightly bloated because marketplace bundles many capabilities and several status/sync tools could be consolidated, but the scope is broad enough that the number is defensible.

Completeness4/5

The toolkit covers the core Open Finance surface thoroughly: accounts, balances, transactions, credit-card bills, loans, investments, categories, connection lifecycle, sync, and provider health, plus marketplace and platform plumbing. Minor gaps exist—no direct connect-bank action beyond URLs, no per-transaction get endpoint, and some marketplace operations are only accessible through the single marketplace tool—but standard workflows are not dead-ended.

Resources