Skip to main content
Glama

Eurekuh

Get one post

get_post_status
Read-onlyIdempotent

One post: whether it went out, its link on the network if it did, and the network's own error message if it did not. firstComment says when its first comment goes out and whether it has.

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_post_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe post id from create_post or list_posts.
organizationIdNoWhich organization to act in: an id from list_organizations. Leave out for this connection's default organization.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already cover safety and idempotency (readOnly, idempotent, non-destructive, openWorld). The description adds real behavioral value by naming the outcome states it can surface (published with link, failed with network error, firstComment timing) – effectively a prose return contract. However, with no output schema, it still leaves the full response shape and error-handling behavior underspecified.

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?

Two short sentences, front-loaded with the resource and then the field-level outcomes, with no filler. The telegraphic 'One post:' opener is slightly clipped but efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-record read with no output schema, the description does explain the key returned signals (delivery outcome, network link, error message, firstComment). It remains incomplete about the rest of the post payload and how pending/scheduled states are represented, which an agent would need.

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 both the id and organizationId parameters are already fully documented in the schema, including where ids come from and the default-organization behavior. The description adds nothing about parameters, so baseline 3 applies.

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 names the resource ('One post') and enumerates what it reports: delivery status, the network link if published, and the network's error message if not. That is more specific than the title, though the verb is only implied by the name get_post_status rather than stated outright.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to call this versus list_posts or the stats tools, and no mention of prerequisites or when-not-to-use. The only usage signal is implicit: it is a per-id lookup rather than a listing.

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