Skip to main content
Glama

EasyCanDo

Get tool records

get_tool
Read-onlyIdempotent

Get the full record of up to 5 tools: each capability with its input and output types, price and limits; API status, sign-up and auth; price tier and free tier; ways in (web API, SDKs, official MCP); docs, pricing and site links; terms; ranking; and the date it was checked. Takes slugs from search_tools, page URLs or tool names. Call it before writing integration code.

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": {
      "slugs": "<slugs>"
    },
    "name": "get_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugsYes1 to 5 tools: slugs from search_tools, easycando.com page URLs or tool names.

Output Schema

NameRequiredDescriptionDefault
toolsYes
missingYesEach reference that matched no tool, with up to five suggested slugs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely new behavioral context: the hard cap of 5 records and the presence of a 'date it was checked' freshness field, which matters for trusting the data. It does not say what happens for unknown or invalid slugs, which is the remaining gap.

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

Conciseness3/5

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

The opening clause is well front-loaded, but the long semicolon-separated field inventory largely duplicates the output schema and makes the first sentence hard to scan. It is dense useful content repeated from structured fields rather than wasted prose, so it is adequate but not tight.

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 a full output schema, annotations, and a fully documented single parameter, the description only needs to convey purpose and call timing, which it does. The missing piece is failure behavior for bad slugs, a small but real omission for a lookup tool keyed on user-supplied identifiers.

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 coverage is 100% and the schema's own description already says 'slugs from search_tools, easycando.com page URLs or tool names', so the description's restatement adds no meaning beyond it. The min/max of 1–5 is likewise already encoded in the schema; baseline 3 applies.

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?

States a specific verb and resource ('Get the full record of up to 5 tools') and enumerates the record contents, which cleanly separates it from search_tools (discovery) and find_chains. An agent knows exactly what it gets back without opening the 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?

'Takes slugs from search_tools' plus 'Call it before writing integration code' gives a clear usage sequence and trigger. It stops short of explicit exclusions or a when-not-to-call statement, so it falls just shy of the top band.

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