Skip to main content
Glama

Jonas Splinter (jsplinter.nl)

Get one update

get_update
Read-onlyIdempotent

One update in full by its slug: date, project, title, text, tags, its URL on jsplinter.nl and the link it points to, if any. Slugs come from search_updates.

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": {
      "slug": "<slug>"
    },
    "name": "get_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesUpdate slug as returned by search_updates, e.g. "site-redesign".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds value with the return-shape disclosure and the 'if any' qualifier signaling the outbound link is optional/nullable — useful since no output schema exists. It does not say what happens when a slug is not found.

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 compact clauses, the payload enumeration is front-loaded immediately after the verb, and the provenance note comes last. No redundant or filler wording.

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 one-parameter read tool with rich annotations and no output schema, the description covers input provenance and returned fields, which is most of what an agent needs. Missing only failure behavior for an unknown slug.

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 single slug parameter already documents 'Update slug as returned by search_updates, e.g. "site-redesign"'. The description's slug-source note largely restates the schema, 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?

States a specific verb and resource ('One update in full by its slug') and enumerates the payload fields (date, project, title, text, tags, URL, outbound link). The mention of search_updates as the slug source distinguishes it cleanly from the search sibling.

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?

'Slugs come from search_updates' establishes the retrieval workflow that selects this tool — find the slug first, then fetch. It stops short of explicit when-not guidance (e.g., use list_updates for browsing several updates), so it is strong but not complete.

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