Skip to main content
Glama

EQI 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. 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"
+}
  10. 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"
+]
  11. 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"
+}
  12. Added
  13. Removed
  14. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description reveals key behaviors: invoke runs one-off without installing, returns connect/checkout links under auth/payment failures, and requires owner/admin for writes. It also explains the distinction between installed_in_toolkit vs installed_in_workspace and the prompt library's purpose. These details go well beyond the generic annotation 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 a single dense paragraph but is front-loaded with the main purpose and every sentence contributes unique information (core flow, invoke behavior, permissions, prompt library). It is appropriately detailed for a multi-action hub, though it could benefit from greater structural organization.

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 (14 actions, 23 parameters, no output schema), the description covers the primary workflows, edge cases (credentials/payment), permission requirements, and the prompt library. It omits some details like the 'resume' action and several parameter meanings, but it provides enough context for an agent to understand the tool's scope and main behaviors.

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 description coverage, the description compensates by explaining the action enum values (search, describe, invoke, install, etc.) and the roles of mcp_id, tool_id, arguments, and prompt_vars. However, many of the 23 parameters (limit, immediate, tier_slug, cancel_reason, report_context, prompt_targets, etc.) remain undocumented, so compensation is only partial.

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, a catalog and execution engine for MCPs/tools, and also a prompt library. It enumerates the core flow (search→describe→invoke) and lists all major actions, distinguishing it from the openfinance sibling tools which are specialized financial connectors.

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 provides explicit guidance: prefer invoke for one-off use over install for permanent additions, use list_tools to see what is callable, use request_mcp when nothing fits, and use subscribe/cancel for billing. It also clarifies prerequisites such as owner/admin for writes and the retry flow when connect/checkout links are returned.

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

All EQI 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

A4.1/5.0
Disambiguation4/5

The openfinance_* tools are clearly separated by resource and action, and their detailed descriptions make most choices unambiguous. However, marketplace is a multi-action mega-tool that duplicates report_bug, and openfinance_list_transactions vs openfinance_list_transactions_by_item have some overlap that could cause misselection.

Naming Consistency4/5

The 19 openfinance_* tools follow a consistent and predictable 'openfinance_<verb>_<noun>' pattern. The non-openfinance tools are a mixed set (marketplace, toolkit_info, show_version, report_bug, authenticate, connect), which is readable but not fully uniform.

Tool Count3/5

25 tools lands right at the heavy end of the borderline range. The Open Finance domain genuinely has many distinct resources, but the marketplace tool alone packs in many sub-actions, which makes the total tool count feel more bloated than the domain strictly requires.

Completeness4/5

The surface covers the full Open Finance lifecycle well: connections, sync/disconnect, accounts, transactions, credit card bills, loans, investments, categories, provider health, and platform administration. Minor gaps exist, such as no direct connect/add-bank tool beyond returning a connect_url and no get-single-transaction endpoint, but agents can work around these.

Resources