Skip to main content
Glama
Sign In
Reletter

Reletter

Official
by getreletter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_issue

Retrieve the full data for a single newsletter issue, including body text and publication details.

Instructions

Full data for a single issue, including the body text and the publication it belongs to.

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": {
      "issue_id": "<issue_id>"
    },
    "name": "get_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
issue_idYesThe Reletter issue ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description reveals that the tool returns full issue data including body and publication. However, it does not disclose other behavioral aspects such as error conditions, rate limits, or authentication requirements.

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?

The description is a single sentence that is front-loaded with the main purpose and includes key details about what data is returned. No unnecessary words.

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 simple get-tool with one parameter and no output schema, the description provides enough context about what data is returned. It could mention that it retrieves from Reletter, but the sibling context clarifies the domain.

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% for the single parameter issue_id. The description adds no additional meaning for the parameter beyond the schema's 'The Reletter issue ID.' The description focuses on output content rather than parameter semantics.

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?

The description clearly states that the tool retrieves full data for a single issue, including body text and the publication it belongs to. This distinguishes it from siblings like list_issues (which returns multiple) and search_issues (which searches).

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?

No guidance is provided on when to use this tool versus alternatives like list_issues or search_issues. The description does not mention prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools