Omie

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.6/5.0

Behavior5/5

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

Beyond the annotations, the description discloses key behaviors: invoke works even when the MCP is NOT installed, returns connect links for credentials, returns checkout links for empty wallets, and 'Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin.' These details add valuable context about side effects and prerequisites.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single dense paragraph without visual breaks or bullets, making it harder to scan. While every sentence adds substantive information, the sheer length (200+ words) and lack of structure detract from conciseness.

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 complexity (23 parameters, 14 actions) and absence of an output schema, the description provides a thorough overview of the tool's functionality, flow, permissions, payment handling, and the separate prompt library. It omits details on some secondary parameters, but the overall context is rich enough for an agent to understand when and how to use it.

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 and does explain the central 'action' parameter and important fields (mcp_id, tool_id, arguments, prompt_slug). However, several parameters like limit, query, immediate, conversation, and prompt_targets remain undocumented in both schema and description, so it doesn't fully compensate for the low coverage.

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 states the tool's purpose as 'the official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them,' and outlines a concrete core flow (search → describe → invoke). This distinguishes it from sibling tools like omie_* which are domain-specific data operations.

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: 'Use install only to make an MCP PERMANENT in the active toolkit ... prefer invoke for a single/occasional use.' It also clarifies when to use list_tools, subscribe/cancel, report_bug, and request_mcp, and 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 Omie 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

The core Omie operations are distinct by resource and action, and the descriptions actively call out edge cases like omie_lancar vs omie_create_payable/receivable and transfer vs manual entries. A few pairs (list_payables/list_receivables/list_financial_movements/list_checking_account_entries) still overlap enough that an agent could pick the wrong one on first attempt.

Naming Consistency4/5

The dominant pattern is clear and consistent: omie_verb_noun with create, get, list, update, delete, settle, cancel, and reconcile. The main deviations are the Portuguese helper omie_lancar and the unprefixed platform-level tools like authenticate, connect, marketplace, and toolkit_info, which break the otherwise regular naming scheme.

Tool Count1/5

With 50 tools, this server is far beyond the 3-15 well-scoped range and sits at the extreme end of the rubric. Most of the tools are individually purposeful, but exposing checkings, payables, receivables, reconciliation, attachments, invoicing, batch upserts, and an entire marketplace platform in one server heavily taxes an agent's tool-selection space.

Completeness4/5

The core financial lifecycle is well covered: create, read, update, delete, settle, cancel, reconcile, unreconcile, transfer, attachment upload, and batch upsert. Minor gaps exist—invoices are list-only, customers have no delete operation, and there is no dedicated get-by-id for checking accounts—but these are workable for the main reconciliation workflows.

marketplace

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources