Skip to main content
Glama

About Eddocu

about_eddocu
Read-onlyIdempotent

What Eddocu is and does: platforms, what is free, plans and prices in USD, the online tools and the blog. "summary" is a short overview; "full" adds every plan, tool and post.

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": "about_eddocu"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNosummary

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, which fully covers the safety profile for a static info lookup. The description adds little beyond that — no note on freshness of pricing data or whether results are cached — so it is adequate but not value-adding on this dimension.

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 tight sentences: the first front-loads what content is available, the second explains the detail parameter. No filler, no restatement of the tool name, and the most decision-relevant information (pricing, free tier) appears early.

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 single-parameter, read-only informational tool with no output schema, the description covers both what is returned in substance and how the detail flag changes it. Only minor gaps remain, such as whether pricing reflects current or cached values.

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 description coverage is 0%, so the description must carry the parameter burden, and it does: it explains that "summary" is a short overview while "full" adds every plan, tool, and post. That is a real semantic distinction beyond the bare enum values and default. It does not discuss output size or cost implications of "full", keeping it from a 5.

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?

The description names a specific resource and enumerates its scope: platforms, free offering, plans and USD prices, online tools, and blog. An agent can tell this is a product/pricing reference tool rather than an action tool. It does not explicitly contrast with the sibling get_app_link, so it stops short of 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 content list implies the usage context (an agent needing product, pricing, or content information about Eddocu), but there is no explicit when-to-use or when-not statement and no named alternative. Guidance is inferable rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources