Skip to main content
Glama

Ergora Specialists

by io.github.ergoracloud
OverviewDiscussionsAdmin

Ergora Content Marketing Specialist

ergora_content
Read-onlyIdempotent

Ask the Ergora Content Marketing specialist (SEO, editorial, distribution, content strategy). Returns summarised, cited insights from a curated knowledge base of practitioners, books and research.

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).
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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive behavior, so the safety profile is covered. The description does add useful output context ('summarised, cited insights from a curated knowledge base'), but it omits the anonymous-vs-email query quota and the fact that 'subscribe' triggers outbound email, which live only in the schema.

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 compact sentences: the first establishes what the tool is and its scope, the second establishes what comes back. Nothing is redundant or 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?

With no output schema, the description usefully characterizes the return as summarised and cited from a curated knowledge base, and annotations cover safety. Minor gaps remain around quota behavior and the email-confirmation side effect, though those are recoverable from the schema.

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%, including the free-tier quota rationale for 'email' and the constraint on 'subscribe', so the schema carries the burden. The description adds no per-parameter meaning beyond what is already documented, which is the expected baseline here.

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?

Names a specific action (ask a specialist) plus the resource domain, and lists the sub-topics it covers (SEO, editorial, distribution, content strategy) so an agent can route by topic. It does not, however, draw an explicit boundary against the overlapping sibling ergora_marketing, leaving topical overlap to inference.

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 domain parenthetical implies when to reach for this specialist versus the other ergora_* domains, but there is no explicit when-to-use statement, no when-not-to-use condition, and no named alternative such as ergora_marketing or ergora_ask. Usage is inferable, not stated.

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