Skip to main content
Glama

Codenation

Get a tool

get_tool
Read-onlyIdempotent

Get the full Codenation record of one tool by its slug (as returned by search_tools): description, makers, category, tags, pricing model, website, the collections it belongs to, and when available a checked presentation with what it does, who it suits, the price read on the tool's own pricing page, the date it was read and the source URL. Returns an error result if the slug is unknown.

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

Input Schema

NameRequiredDescriptionDefault
slugYesTool slug, e.g. "plausible-analytics".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the bar is lower; the description still adds real context by naming the exact record contents, flagging that the "checked presentation" is only present "when available", and stating that an unknown slug yields an error result rather than a silent empty response.

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?

One front-loaded sentence with the verb and lookup key first, followed by the payload list and the error condition. The enumeration of returned fields is long but every item adds information an agent would otherwise have to discover by calling the tool.

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 carries the return-value burden and does so by itemizing the record fields plus the conditional presentation block with its read date and source URL. The only gap is any sense of record size or truncation behavior, which is minor for a single-record lookup.

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 100% with a worked example, so the baseline is 3; the description goes beyond it by explaining the provenance of the slug value (it comes from search_tools output), which is what makes the parameter actionable rather than just typed.

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 opens with a specific verb and resource ("Get the full Codenation record of one tool by its slug") and then enumerates the payload, so an agent can distinguish it from search_tools (discovery) and get_collection (collection-scoped) without opening any 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 routes the agent to the sibling that produces the required input via "as returned by search_tools", making the discovery-then-fetch sequence explicit. It lacks an explicit statement of when not to use it (e.g. when you only need a listing), which keeps it short of a 5.

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