Skip to main content
Glama
OmniExtract MCP

OmniExtract MCP

omni_check_quota

Check remaining API key credits or daily anonymous free quota to monitor usage and avoid failed requests.

Instructions

Check remaining API key credits or daily anonymous free quota.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "omni_check_quota"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNoOptional OmniExtract API key (omni_live_...).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. It discloses the two quota modes it reports on, which is meaningful behavior beyond the schema, but says nothing about whether the check itself consumes quota, what the response shape looks like, or what errors occur with an invalid or expired key. Those are real gaps for a tool with zero annotation coverage.

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

Conciseness5/5

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

A single sentence with every word load-bearing, front-loaded with the verb and the two resources. Nothing redundant, nothing buried.

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?

This is a simple, single-optional-parameter read tool with no output schema and no annotations, so the bar for description completeness is modest. The description covers the purpose and both quota modes adequately; only the error behavior and whether checking consumes quota are left unstated, which are minor omissions at this complexity level.

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?

Schema coverage is 100%, so the baseline is 3, but the description earns an extra point: it explains the semantic consequence of the optional api_key parameter — with a key you check key credits, without it you check the anonymous daily free quota. The schema only says 'Optional OmniExtract API key'; the description supplies the branching meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb-plus-resource: 'Check remaining API key credits or daily anonymous free quota.' An agent immediately knows this is a quota/credit inspection tool, not an extraction tool, so it is clearly distinguishable from the omni_extract_* siblings by function. It stops short of an explicit contrast with those siblings, hence not a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'or' construction implicitly tells the agent that supplying an API key inspects key credits while omitting it inspects the anonymous daily quota, which is a useful usage signal. However, there is no explicit when-to-use framing, no mention of calling it before extraction, and no stated alternatives or exclusions. Usage is implied rather than guided.

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