Skip to main content
Glama

Get a Pulse article

flypost_get_article
Read-only

Read one article including its markdown body, cited sources, target keyword, and its brief (outline sections and candidate sources, with the ids flypost_update_article_brief acts on).

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": {
      "article_id": "<article_id>"
    },
    "name": "flypost_get_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
article_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real value by disclosing what the response contains, including nested brief sections and candidate sources, though it says nothing about behavior for a missing or invalid article_id.

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?

One front-loaded sentence that leads with the verb and resource, then lists the returned parts. The trailing parenthetical about brief sections and candidate sources is dense but earns its place by explaining the update-tool linkage.

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 single-parameter read-only tool with no output schema, the description adequately covers return contents and the downstream consumer of the brief ids. The remaining gaps are the article_id format and error behavior, which are minor for an operation this simple.

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 0%, and article_id has no documentation in either schema or description. 'Read one article' implies the parameter identifies a single article, but its expected format (id, slug, uuid) is left unstated.

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 one article') and enumerates the payload it returns: markdown body, cited sources, target keyword, and brief. It also names the sibling it feeds data into (flypost_update_article_brief), which distinguishes it from related article tools like flypost_get_draft.

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?

Clear context: use this to fetch an article's content and the brief ids that flypost_update_article_brief consumes, which is a genuine workflow cue. It stops short of stating alternatives or when not to use it (e.g., versus a draft fetch), so there is no explicit exclusion.

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.