Skip to main content
Glama

resource_get

Read-onlyIdempotent

Read native files, source, license, current hashes, and related bundles for a resource ID before judging simulation applicability.

Instructions

Read native files, source/license, current hashes and related_bundles. Read the bundle's usage/element mapping before judging applicability; multi-element file names alone do not exclude single-element use. File verification and scientific validation are separate.

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_id": "<resource_id>"
    },
    "name": "resource_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
resource_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description adds genuine context beyond that: what data classes come back, an interpretive caution about multi-element file names, and the distinction between file verification and scientific validation — a domain caveat the agent could not infer from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, no filler, and the retrieval scope is front-loaded. However, the second and third sentences are interpretive warnings rather than invocation guidance, and terms like 'usage/element mapping' and 'related_bundles' are used without definition.

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

Completeness3/5

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

An output schema exists, so the description doesn't need to detail return values — yet it partly duplicates that by listing fields. More importantly, it omits what resource_id means and how this tool relates to sibling read tools, which are the gaps that matter for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single required parameter resource_id is never explained in the description. Whether this identifier refers to a bundle, a file, or a catalog entry is only vaguely implied by the phrase 'the bundle's usage/element mapping', leaving real ambiguity for a required key.

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 verb 'Read' plus an enumeration of what is retrieved (native files, source/license, current hashes, related_bundles) makes it clear this fetches a single resource's details. It stops short of distinguishing itself from near-neighbors like resource_file_read or resource_bundle, so an agent can't fully separate them from the description alone.

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?

The guidance present ('read the bundle's usage/element mapping before judging applicability') concerns interpreting results, not selecting this tool over siblings. There is no statement of when to call resource_get versus resource_search, resource_file_read, or resource_bundle.

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