LegendKeeper MCP

get_resource

Read-onlyIdempotent

Fetch a LegendKeeper resource's details by ID, exact name, or alias, including path, tags, documents, sidebar facts, and children; use read_document for document content.

Instructions

Get one resource's details: path, tags, aliases, icon, banner, documents, sidebar properties (facts) and children. Use read_document to read a document's content.

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": {
      "resource": "<resource>"
    },
    "name": "get_resource"
  }
}

Input Schema

Name	Required	Description	Default
`project`	No	Configured project (world) name. Omit to use the default project; see list_projects.
`resource`	Yes	Resource id, or its exact name/alias (case-insensitive).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Oct 17, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds a real behavioral fact beyond that: the call returns document references/metadata rather than document content, which the agent must fetch separately via read_document. It does not cover error behavior for missing resources, but the annotations lower the bar.

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 sentences with no filler; the return-field enumeration comes first and the sibling routing second. Every clause carries information the agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the return-value burden, and it does so by enumerating the fields returned. Combined with rich annotations and a fully documented two-parameter schema, nothing essential for correct invocation is missing.

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%, so both 'project' (project name, omit for default, see list_projects) and 'resource' (id or exact name/alias, case-insensitive) are fully documented in the schema. The description adds no syntax or lookup guidance for either parameter, so the 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 (get) and resource (one resource's details) and then enumerates exactly what is returned: path, tags, aliases, icon, banner, documents, sidebar facts, and children. It also separates itself from the read_document sibling, so an agent can tell it apart 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?

The description routes the agent explicitly: use this to fetch resource metadata, and 'Use read_document to read a document's content.' That names an alternative and the condition selecting it, but it does not say when to prefer this over browse_tree or search for locating a resource.

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