Skip to main content
Glama

Link to the Eddocu app

get_app_link
Read-onlyIdempotent

The install link for one platform (ios, android, windows, mac) or "app", one link that picks the right store for the device that opens it. Linux and every installer: https://eddocu.com/download.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "platform": "<platform>"
    },
    "name": "get_app_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description's added value is that Linux has no per-platform link and a fallback URL exists, which prevents a wasted or failing call, but it says nothing about the shape of the return value (bare string vs object) or whether links are stable/versioned.

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

Conciseness4/5

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

Two short sentences, front-loaded with the per-platform case before the exception, with no filler. The nested quoting around "app" is slightly awkward to parse but does not obscure meaning.

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 lookup with no output schema, the description covers the enum semantics, the special "app" case, and the unsupported-platform fallback, which is essentially everything needed to invoke it correctly. Only the return type and error behavior are left implicit.

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 0%, so the description must carry the parameter meaning, and it does: it lists the concrete enum values and explains the non-obvious "app" option as a single device-adaptive link. It leaves no parameter unexplained, though it does not say whether values are case-sensitive or what happens on an invalid value.

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 the resource concretely ("the install link for one platform") and enumerates the supported platform values, so an agent knows this tool resolves a store/install URL. It stops short of a crisp verb like "return" and never contrasts with the sibling about_eddocu, but the resource and scope are unambiguous.

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 tells the caller which platform key to choose, including the subtle case that "app" yields one link that redirects per device, and it redirects Linux/installer callers to a fixed URL instead of calling the tool. That is real selection guidance, though there is no explicit statement of when to prefer this over about_eddocu or other informational tools.

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