Skip to main content
Glama

Get entry details

get_entry
Read-onlyIdempotent

Show the user one whole entry of Daawid's registry, by its ID, slug or a website its owner proved control of (domain): what it offers with prices, whether it takes on work, hours, contact details, policies and legal details, as its owner declared them. Apps show it as a card. Not needed before a request, whose own card names the entry.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_entry"
  }
}

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 and its card come in it, when the entry has it.

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

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered; the description adds useful context beyond them by stating the content is owner-declared and presented to the user as a card. It does not mention size, truncation, or behavior when an entry lacks the requested language, but for a read tool that is a minor gap.

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 lookup mechanism is front-loaded and the trailing sentences about card rendering and the request exception are short and purposeful. The middle enumeration of returned fields is long but each item conveys what the agent will get, so little is wasted.

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?

With an output schema and full annotation coverage, the description mainly needs to convey lookup semantics and usage, which it does, including the language effect on the response. The only real omission is how it differs from the other entry-scoped read tools (`get_entry_sections`, `get_offerings`, `get_brand_kit`).

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%, so all four parameters are already documented in the schema, giving a baseline of 3. The description confirms that ID, slug and `domain` are alternative identifiers and that `language` drives the answer and card language, but this largely restates the schema rather than adding new syntax or constraint detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ("Show the user one whole entry of Daawid's registry") plus the three lookup keys, and enumerates the payload (offerings and prices, availability for work, hours, contact, policies, legal details). It partially distinguishes itself from `get_entry_sections`/`get_offerings` only implicitly through "one whole entry", and its explicit exclusion targets the request tools rather than the read siblings.

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 provides a concrete when-not rule: "Not needed before a request, whose own card names the entry", which steers the agent away from redundant lookups. It lacks a positive when-to statement relative to other read tools such as `get_entry_sections` or `get_offerings`, so the agent must infer that this is the full-object read.

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