Skip to main content
Glama
Sign In
context-archive

context-archive

by urcades
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_blob

Read-only

Retrieve a stored blob from a read-only archive by hash, using offset and limit to control how much data is returned.

Instructions

Get blob; bounded read-only archive retrieval.

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": {
      "hash": "<hash>"
    },
    "name": "get_blob"
  }
}

Input Schema

NameRequiredDescriptionDefault
hashYes
limitNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's 'read-only' adds no new information. The term 'bounded' hints at pagination (limit/offset) but is too vague to disclose actual behavior like error handling or data size limits. With annotations present, the bar is lower, but the description adds minimal context.

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

Conciseness2/5

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

One short sentence is technically concise, but it is under-specification rather than effective conciseness. There is no front-loading of key information beyond the name, and the structure offers no scannable detail for the agent.

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

Completeness1/5

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

For a tool with 3 parameters, no output schema, and a sibling decode_blob, the description is grossly incomplete. It does not define what a blob is, what 'archive' refers to, how to obtain a hash, or what the response contains. An agent cannot reliably use this tool without external knowledge.

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%, so the description must explain parameters. It does not mention 'hash', 'limit', or 'offset' at all. The word 'bounded' vaguely implies limits, but the agent gets no guidance on what 'hash' identifies or how pagination works. This is a significant gap.

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 'Get' and resource 'blob' clearly state the action, and 'bounded read-only archive retrieval' hints at scope. However, it does not differentiate from siblings like decode_blob or search, leaving the agent to guess which tool fits a given need.

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?

No guidance on when to use this tool versus alternatives. It never mentions decode_blob for decoding or search/query for broader retrieval. The agent must infer usage from context, which is weak for a tool with a sibling named decode_blob.

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

Deploy Server

Other Tools