Skip to main content
Glama
Sign In
Reletter

Reletter

Official
by getreletter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

contacts

Retrieve email addresses, contact pages, social account links, and contributor details for a newsletter by providing its Reletter publication ID.

Instructions

Email contacts, contact pages, and social accounts for a newsletter. Includes contributors where Reletter has identified them.

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": {
      "publication_id": "<publication_id>"
    },
    "name": "contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
publication_idYesThe Reletter publication ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It only mentions 'includes contributors where Reletter has identified them.' It does not disclose read-only nature, authentication needs, or any other behavioral traits.

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 concise sentences with no wasted words. Front-loaded with the key information about what is returned.

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?

Given one parameter and no output schema, the description is adequate but lacks behavioral details and does not specify return format. It is minimally complete for a simple tool.

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% with one parameter (publication_id) described as 'The Reletter publication ID.' The tool description does not add extra meaning beyond the schema, so baseline 3 is appropriate.

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 the tool returns email contacts, contact pages, social accounts, and contributors for a newsletter. It specifies the verb (returns) and resource (contacts) and distinguishes from sibling tools like search and list, which are about publications and issues.

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 on when to use this tool versus alternatives. It does not mention when not to use it or provide exclusions. Siblings do not include a similar contact tool, so context is weak.

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