Skip to main content
Glama

cOBD

Read a news post

read_news
Read-onlyIdempotent

The text of one public post. Use a slug from list_news.

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": {
      "slug": "<slug>"
    },
    "name": "read_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe post's slug

Output Schema

NameRequiredDescriptionDefault
urlYes
dateYes
textYes
titleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is known. The description adds only that the post is "public," which implies access scope. It does not say what happens for a missing slug or an unpublished post, and it names no rate or cache behavior.

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 short sentences with no waste. The outcome is stated first and the prerequisite second, which is the correct order for this simple read tool.

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?

This is a simple one-parameter read tool with an output schema and full annotations. The description covers purpose, required input, and where to find the slug. Only edge-case behavior, such as unknown or private slugs, is missing.

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?

Schema description coverage is 100%, so the baseline is 3, but the description goes beyond the schema by specifying the slug's provenance (from list_news). It still does not state the slug format or whether case matters, and enums are not applicable here.

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 a specific resource and scope: "The text of one public post." That lets an agent distinguish this single-post read from list_news, which only enumerates posts. It is clear, but it does not explain what the returned text contains or how the slug is resolved.

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?

"Use a slug from list_news" gives a clear prerequisite and tells the agent to obtain the required identifier from the sibling tool. No exclusion, such as what to do when the post is private or the slug is unknown, is stated.

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