Skip to main content
Glama

GTM Daily

About the newsletter

get_newsletter_info
Read-onlyIdempotent

Where to read and subscribe to the GTM Daily newsletter.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_newsletter_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
okNo
codeNo
dataNo
statusYes
messageNo
warningsNo
next_stepNo
next_cursorNo
action_grantNo
approval_urlNo
correlation_idYes
missing_fieldsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds only that the result concerns reading/subscribing locations — no mention of staleness, external links, or side effects (e.g. whether subscription is performed or merely pointed to).

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?

A single short sentence with no filler and no burying of key information. It is not padded, though it is arguably under-specified rather than maximally 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 zero-parameter, read-only tool with an output schema and full annotation coverage, little description is required. Still, the reader cannot tell whether calling it yields URLs, an about-page summary, or subscription instructions, leaving a small but real gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and the schema is effectively empty, so there is nothing for the description to disambiguate. Baseline for a no-param tool applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The sentence identifies the resource (GTM Daily newsletter) and hints at the payload (where to read and subscribe), but there is no verb stating what the tool returns or does — an agent has to infer 'returns links/info' from 'Where to read and subscribe'. It is distinguishable from siblings by topic, but the operation itself is vague.

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 indication of when to call this versus sibling tools such as search_gtm_knowledge or get_resource, and no stated prerequisites or exclusions. The topic alone implicitly scopes it, which is the only guidance present.

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