Skip to main content
Glama

Codethrift

Get an entry

get_entry
Read-onlyIdempotent

One entry in full: commit, README, commons.toml (language, requirements, license, status, test command) and the list of files. Pin the returned commit when you reuse the 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": {
      "repo": "<repo>"
    },
    "name": "get_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoBranch, tag or commit. Defaults to the default branch.
repoYesRepository as owner/name, for example commons/film-scan-health.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety is covered. The description adds non-obvious context: the response is complete rather than partial ('in full') and the returned commit should be pinned for reproducible reuse. It does not discuss failure modes for missing repos/refs, but the added workflow detail clears the annotated baseline.

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, front-loaded with the return payload and closed by an actionable reuse rule. Every phrase carries information; no filler or restatement of the title.

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 burden of describing the return value, and it enumerates the fields well. For a two-parameter read tool with full annotation coverage, that is nearly sufficient; only edge-case behavior (invalid repo, unknown ref) is unstated.

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 already explains that ref defaults to the default branch and that repo is owner/name. The description's only added meaning is the implicit link between the returned commit and future ref values. Baseline 3 applies since the schema does the heavy lifting.

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?

The description states a specific resource and enumerates the payload: 'One entry in full: commit, README, commons.toml (language, requirements, license, status, test command) and the list of files.' An agent knows exactly what it gets. It stops short of naming how it differs from siblings such as read_file or search, which keeps it from a 5.

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

Usage Guidelines3/5

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

Implicit guidance only: fetch a whole entry when you need the manifest plus README plus file list, and 'Pin the returned commit when you reuse the code' gives a downstream workflow rule. There is no explicit when-not or pointer to read_file/search for partial reads, which is the main gap.

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