Skip to main content
Glama

Get parts of an entry

get_entry_sections
Read-onlyIdempotent

Read only some parts of an entry, with no card: its actions before a request, say, or its hours. To show the user the entry, use get_entry.

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

Input Schema

NameRequiredDescriptionDefault
idNoIts ID, from search: "ent_…".
slugNoIts slug, the end of its address: "example-bakery".
domainNoA website its owner proved control of.
languageNoThe language the user writes in: "en". The answer comes in it, when the entry has it.
sectionsYesThe parts of the entry to read.

Output Schema

NameRequiredDescriptionDefault
idYes
kindYes
slugYes
linksYes
listedYes
statusYes
summaryYes
languageYes
revisionYes
languagesYes
displayNameYes
schemaVersionYes
defaultLanguageYes
availableLanguagesYes

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 readOnly/idempotent/destructive=false, so the safety profile is covered. The description adds genuine context beyond them: the result carries 'no card' (raw section data rather than a rendered entry) and only the requested parts are returned. It stops short of describing response shape or limits, but that is acceptable given an output schema exists.

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 sentences, zero padding, with the scope constraint and the alternative front-loaded in that order. Every clause earns its place.

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?

A simple partial-read tool with four annotation hints and a full output schema; the description needs to convey scope and sibling routing, which it does. Identification of the entry (by id, slug, or domain) is left entirely to the schema, a minor gap only.

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 schema alone carries the parameters; the description contributes only illustrative section examples ('actions before a request', 'hours'). No added meaning for id/slug/domain identity selection or the language effect beyond what the schema states.

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 (read only some parts of an entry) and explicitly scopes it against the sibling that returns the whole entry: 'To show the user the entry, use get_entry.' An agent can distinguish it from get_entry and the section-specific siblings without opening a schema.

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

Usage Guidelines5/5

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

Gives both the when ('read only some parts... its actions before a request, say, or its hours') and the when-not plus alternative ('To show the user the entry, use get_entry'). The routing condition is stated outright, not implied.

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