Skip to main content
Glama
mcp-server-starter

mcp-server-starter

by humzagk

Get item

get_item
Read-only

Retrieve a full help-centre article by its id to read its complete content after finding it with search.

Instructions

Read one of the help-centre articles in full, by id.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe item id, as returned by search_items

Output Schema

NameRequiredDescriptionDefault
idYes
uriYes
titleYes
contentYes
metadataNo
updatedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the meaningful behavioral detail that the article is returned 'in full' rather than as a snippet, which tells the agent to expect complete body content; it does not, however, mention truncation or missing-item behavior.

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?

A single short sentence with no waste, front-loading the verb and resource before the scoping qualifier. Nothing could be removed without losing meaning.

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?

An output schema exists, so return values need no explanation, and the single required parameter is fully documented in the schema. For a simple read-by-id tool the description is nearly sufficient; only error/not-found behavior is unaddressed, which is a minor gap.

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?

Only one parameter, and the schema already documents it fully at 100% coverage, including length bounds and the source of the id. The description's 'by id' merely restates that, adding no format or provenance detail beyond the schema.

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 (read), resource (help-centre article), and scope (one, in full, by id). 'In full' distinguishes it from the snippet-level results a search tool would return, so an agent can tell it apart from search_items without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the id parameter's schema note ('as returned by search_items') establishes the search-then-fetch flow, but the description itself never says when to prefer this over search_items or what happens for an unknown id. An agent can infer the pattern, but it is not spelled out.

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