Skip to main content
Glama

Copybook

Check installed Copybook text

check_installed
Read-onlyIdempotent

Checks Copybook text already in a repo by the IDs in its From Copybook source lines: #<8 hex> (the slug of the source URL with each block or unit ID), up to 100, IDs only (no paths or file contents). Each ID is current (the tip still has that text; local edits are not checked) or changed (the tip no longer has it). Also reports each tip as live, superseded (with its replacement) or retired (its latest check broke), with checks and durability. Without IDs, get_tip returns the current text to compare. Needs a Copybook sign-in; without one, the result's message says how to sign in from this client.

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": {
      "ids": "<ids>"
    },
    "name": "check_installed"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesThe IDs from the source lines above Copybook text in the repo, up to 100, each <slug>#<8 hex>: the slug from the line's URL, then each block or units ID. Never file contents or paths.

Output Schema

NameRequiredDescriptionDefault
tipsYes
messageYes
unknownYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the read-only and non-destructive annotations, the description discloses key behavior: local edits are not checked, each ID resolves to current or changed, and each tip is reported as live, superseded, or retired. It also explains the sign-in dependency and what happens without authentication.

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?

The purpose is front-loaded and every clause carries information, but the single dense paragraph is somewhat run-on with parentheticals and semicolon-separated ideas. It is concise but could be easier to scan if split by usage, result semantics, and authentication.

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

Completeness5/5

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

Given the single required parameter, rich schema, annotations, and output schema, the description covers what an agent needs: input origin and constraints, result semantics, the get_tip alternative, and the sign-in requirement. The vague phrase 'with checks and durability' is acceptable because the output schema can carry return-value detail.

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 already 100%, so the schema carries the formal validation rules. The description still adds useful meaning by explaining that IDs come from From Copybook source lines, encode the source URL slug plus block or unit ID, and must never be file contents or paths.

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?

The description states a specific verb and resource: it checks Copybook text already in a repo by IDs drawn from source lines. It also defines the ID shape and clarifies that only IDs, not paths or file contents, are accepted, which lets an agent distinguish this from the sibling get_tip.

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?

It gives a clear usage context: use source-line IDs, up to 100, and call get_tip instead when no IDs are available. It also notes the sign-in requirement, though it does not give a broader explicit when-not-to-use rule beyond the missing-ID alternative.

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