Skip to main content
Glama

Get one Klarhimmel UI item

get_item
Read-only

Read-only and free. One item by its exact name (from search_items): title, description, the install command, its page URL and Markdown twin URL, and its dependencies.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe item name, e.g. "pricing-tiers".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint=false, so safety is covered; the description still adds 'free' (no cost/rate concern) and the exact-name matching requirement, plus an itemized return payload in the absence of an output schema. It does not say what happens when the name is not found, which is the main remaining gap.

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, front-loaded with the safety/cost profile, then the input requirement and the return contents. No filler.

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 single-parameter read with no output schema, listing the returned fields plus the name provenance covers nearly everything an agent needs. Only the not-found behavior is left implicit.

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 100% with a single documented parameter, so the baseline is 3; the description earns an extra point by specifying that the match must be exact and by pointing to search_items as the source of valid names.

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 item by its exact name') and enumerates exactly what comes back: title, description, install command, page URL, Markdown twin URL, and dependencies. This is clearly distinct from search_items, which is named as the source of valid names.

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?

The parenthetical '(from search_items)' establishes the workflow prerequisite: obtain the name via search_items, then fetch it here by exact name. There is no explicit when-not or failure guidance, but the selection context is clear.

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