Skip to main content
Glama

Ergora Specialists

by io.github.ergoracloud
OverviewDiscussionsAdmin

Ask all Ergora Specialists

ergora_ask
Read-onlyIdempotent

Ask across all 17 Ergora specialists at once (cross-vertical). Use a specific ergora_ tool when you know the domain.

Input Schema

NameRequiredDescriptionDefault
emailNoOptional. The user's email. Unlocks the free tier (30 queries a day instead of 5 anonymous). Ask the user once, then pass it on every call.
queryYesThe question or topic to research (natural language).
top_kNoHow many insights to return (1-10).
verticalNoOptional: restrict to one vertical slug.
subscribeNoOptional. Set true only if the user explicitly asks for Ergora updates by email. Sends one confirmation link to that address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / subscribe
      Added value: +{
+  "description": "Optional. Set true only if the user explicitly asks for Ergora updates by email. Sends one confirmation link to that address.",
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / email / description
      Previous value: -"Optional. The user's email — unlocks the free tier (30 queries/day vs 5/day anonymous). Ask the user once, then pass it on every call."New value: +"Optional. The user's email. Unlocks the free tier (30 queries a day instead of 5 anonymous). Ask the user once, then pass it on every call."
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so safety is covered. The description adds the fan-out scope (all 17 specialists) but says nothing about throughput limits, the free-tier/email unlock, or the shape of what comes back — all of which matter for a network-backed query tool.

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?

Two short sentences, zero filler, with the primary capability front-loaded and the alternative routing second. Every clause carries decision-relevant information.

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?

For a five-parameter read-only query tool with full schema coverage and a complete annotation set, the description covers the essential routing decision. It stops short of noting the daily quota / subscription behavior that affects real invocation choices, but no output schema exists to compensate for return-shape ambiguity.

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?

Schema description coverage is 100%, so email, query, top_k, vertical, and subscribe are all documented in the schema, and the baseline is 3. The description only loosely reinforces the 'vertical' parameter by telling the agent to prefer the per-vertical tool; it adds no syntax or defaulting detail beyond the schema.

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 states a specific verb+resource+scope: asking across all 17 Ergora specialists at once, cross-vertical. It also names the contrasting sibling pattern (ergora_<vertical>), so an agent can distinguish it from the 17 vertical tools without opening a schema.

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

Usage Guidelines4/5

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

It gives a clear routing rule: use this for cross-vertical questions, use a specific ergora_<vertical> tool when the domain is known. That covers the main when/when-not decision, but it doesn't address the other plausible alternatives such as ergora_list_specialists or clarify that trivial lookups are a poor fit.

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

All Ergora Specialists toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources