Skip to main content
Glama

Emergent.FM

One entry

get_item
Read-only

One published entry by id, like "item-45", "story-6" or "wire-123". An id that is not published, or a deleted story, is not found.

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
idYesAn entry's id: its "_emergent_fm" kind and id joined by a hyphen, like "item-45", "story-6" or "wire-123".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, non-destructive, closed-world), and the description adds real behavioral detail beyond them: only published entries are retrievable, and unpublished ids or deleted stories resolve to not-found. That not-found semantics is exactly the kind of outcome an agent needs to plan around; only the return shape is left unstated.

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 sentences, front-loaded with the resource and lookup key, then the failure case. Every clause carries information and nothing is redundant padding.

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 lookup with full schema coverage and complete annotations, the description covers scope and error behavior adequately. The only gap is that it never hints at what an entry contains, which matters somewhat since no output schema exists.

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% and the single parameter is fully documented there, including the same example ids and the hyphen-joined kind pattern. The description repeats those examples rather than adding new constraints, so it sits at the baseline for a fully specified schema.

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?

States a specific retrieval action on a specific resource ('One published entry by id') with concrete id examples, which cleanly separates it from the date-ordered and search siblings. It stops short of naming an alternative tool, but the 'by id' framing makes the distinction evident.

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 only implied: the agent must infer that this tool is for when it already holds a concrete entry id. There is no explicit statement of when to prefer items_by_date, latest_items, or search_items instead, and no prerequisite guidance on where ids come from.

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