Skip to main content
Glama
Sign In
buddie

buddie

by tsyyan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

snap

Read-onlyIdempotent

Snapshot web pages before quoting them so claims can be checked against stored source text and linked to the exact URL.

Instructions

Snapshot URLs (bytes by sha256) so quotes can be taken from and checked against them. Call it before quoting a page, then copy the words from source_text and link the same URL.

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": {
      "urls": "<urls>"
    },
    "name": "snap"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesthe pages to fetch (http or https), one snapshot each; a failure is recorded too
storeNosnapshot store (default $VERBATIM_STORE or ./.verbatim)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.0
    • addedInput schema / properties / store / description
      Added value: +"snapshot store (default $VERBATIM_STORE or ./.verbatim)"
    • addedInput schema / properties / urls / description
      Added value: +"the pages to fetch (http or https), one snapshot each; a failure is recorded too"
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, open-world, idempotent, and non-destructive behavior. The description adds useful behavioral context by saying snapshots store bytes keyed by sha256 for later checking, though it omits return format, error handling, and authentication/rate-limit details.

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 short sentences with the core action front-loaded, followed by the workflow instruction. There is no filler or redundancy.

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?

For a simple two-parameter tool with rich annotations and complete schema coverage, the description gives enough context to invoke it correctly in the quoting workflow. Since there is no output schema, it could say more about what a snapshot returns or how to reference it later, so it is not fully complete.

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 the urls array and store parameter are already documented in the schema. The description reinforces linking the same URL but adds no new meaning for the store parameter or array behavior, 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?

Starts with a specific verb and resource: 'Snapshot URLs', and explains the purpose via 'bytes by sha256' and quote verification. It also distinguishes itself from the source_text sibling by saying to call snap first, then copy words from source_text.

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?

Explicitly says to call it before quoting a page and then use source_text, giving clear workflow context. It does not state when not to use it or name an alternative snapshot route, so it falls short of full when/when-not guidance.

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