Skip to main content
Glama

Read one entry

get_entry
Read-onlyIdempotent

Fetch one skill, agent, or command by ID or name to inspect its frontmatter and body; use source to disambiguate duplicate names.

Instructions

Read one skill, agent or command by id or name, including its frontmatter and body. The id is skill:<source>:<name>, and the shorter skill:<name> and a bare name also resolve. Not covered by get_entry_bundle, which also returns supporting files.

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_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesEntry id or name.
sourceNoRestrict to one source id when the name is ambiguous.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: id resolution accepts `skill:<source>:<name>`, shorter `skill:<name>`, or a bare name, and it discloses the return payload (frontmatter plus body). It does not say what happens on ambiguous or unresolvable names, which is the remaining behavioral gap.

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?

Three short sentences, front-loaded with what is read and returning the id format before the sibling caveat. The fragment 'Not covered by get_entry_bundle, which also returns supporting files.' is slightly awkward and negative-first, but it is tight and does not waste words.

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, describing the returned frontmatter and body is appropriately included. For a 2-parameter read tool the coverage is nearly sufficient; only the behavior on ambiguous/non-matching ids and how `source` interacts with resolution is left to inference.

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% and the schema only says 'Entry id or name' for the id field; the description supplies the actual id grammar and the fallback resolution rules, which is meaning the schema does not carry. The `source` parameter's ambiguity-disambiguation purpose is only implied ('when the name is ambiguous' lives in the schema, not the description).

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 precise verb and resource ('Read one skill, agent or command by id or name') plus what is returned ('its frontmatter and body'). It also names the sibling get_entry_bundle and the specific difference (supporting files), so the agent can separate the two without opening either 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 closing sentence establishes the alternative and when it wins: use get_entry_bundle if supporting files are needed. That is a real exclusion, though the description never says the inverse case positively (e.g. 'use this when you only need the entry content'), so the selection rule is implied rather than fully stated.

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