Skip to main content
Glama

Get one Actor's details

get_tool
Read-onlyIdempotent

Everything published about one catalogue Actor: description, price, required and example input, output fields, MCP URL, configs for Claude Code/Cursor/VS Code/Codex, n8n workflow, SKILL.md and schema files, matching recipes.

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

Input Schema

NameRequiredDescriptionDefault
idYesActor id owner/name (from search_tools), or its recipeforagents.com or Apify Store URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety is covered; the description adds real value by disclosing exactly what content comes back, which matters since no output schema exists. The gap is failure behavior: nothing says what happens when the id doesn't resolve to a published Actor.

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 that opens with the core purpose and then lists payload contents; the comma-delimited feature list is dense but every item is informative and there is no filler or repetition.

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 simple one-parameter read tool with no output schema, the description does the heavy lifting by enumerating returned fields, and the schema fully documents the id. Only the not-found / invalid-id behavior is left unaddressed.

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% for the single 'id' parameter, including the owner/name format, length cap, and that a recipeforagents.com or Apify Store URL is also accepted. The description adds no meaning beyond that, so the baseline 3 applies.

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?

States a specific verb+resource: fetching 'everything published about one catalogue Actor', then enumerates the payload (description, price, input/output fields, MCP URL, configs, workflow, SKILL.md, recipes). This clearly distinguishes a single-Actor detail lookup from search_tools or get_recipe, though it never names those siblings to make the contrast explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance. The description never says to call this after search_tools, never contrasts it with get_recipe, and never explains what to do if the id is unknown or invalid — that the id comes 'from search_tools' appears only in the schema, not the description.

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