Skip to main content
Glama

PicPay MCP

by io.github.mcp-dir
OverviewAdmin

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. 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"
+}
  6. 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"
+]
  7. 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"
+}
  8. Added
  9. Removed
  10. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The description goes far beyond the minimal annotations, disclosing key behavioral traits: invoke works even when an MCP is not installed and runs it one-off without bloating the toolkit; credentials trigger a connect link; empty wallet triggers a checkout/top-up link; writes require workspace owner/admin. It also explains the installed_in_toolkit vs installed_in_workspace flags and the one-off install behind invoke. This rich context is not present in the 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 a single dense paragraph, but it is information-dense with no fluff — every sentence adds value. It could be better structured with bullet points, but given the tool's 14 actions and prompt library scope, the length is justified. It is front-loaded with the core definition and flow.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the complete tool landscape: core flow, installation vs invocation, auth and billing edge cases, workspace owner permissions, installed flags, prompt library, and when to use request_mcp. Despite having no output schema, it gives enough context for an agent to select and invoke the right action, including error-handling behavior (connect/checkout links and retry).

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 carries the burden of explaining parameters. It maps the action enum to specific behaviors (search, describe, invoke, install, subscribe, etc.) and explains the role of tool_id and arguments in the invoke flow ('pick the right tool_id → invoke RUNS that tool'). It also covers prompt-related params via get_prompt and publish_prompt. However, some params like limit, immediate, conversation, and prompt_targets are not explicitly explained, leaving a small gap.

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 opens with a clear definition: 'The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them.' It specifies the scope (cataloging and running MCPs) and distinguishes itself from sibling tools like openfinance_* which are specific financial MCPs. The core flow (search → describe → invoke) is explicitly stated, making the tool's purpose unmistakable.

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 when-to-use guidance: 'use install only to make an MCP PERMANENT... prefer invoke for a single/occasional use.' It also contrasts subscribe/cancel for billing, report_bug for feedback, and request_mcp for new MCP requests. The description clearly states when to choose the prompt library actions (search_prompts/get_prompt/publish_prompt) versus MCP actions, and even covers the fallback when nothing fits.

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

All PicPay 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.

Resources