Skip to main content
Glama

Get an article summary

get_article
Read-onlyIdempotent

Get a NonToxicFinder article summary by slug: its title, excerpt, frequently asked questions and the products it features, in the order the article shows them. Link people to the url given in each result and never construct a retailer link. Say "last read on " for a certification. Say "brand-level" when evidence_scope is "brand". Ratings are scores, not certifications.

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": "get_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, and the description adds real context on top: results preserve the article's display order, URLs must be taken verbatim from the response, and certification/evidence_scope/rating semantics are spelled out. It does not cover failure behavior for an unknown slug, keeping it below a 5.

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?

It is compact and front-loaded, leading with what is returned before the presentation rules. The first sentence is a long run-on that packs return fields and ordering together, but no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of explaining return values, and it does: it names the returned fields, the ordering, the url field, evidence_scope values, and certification dates. For a single-parameter read tool this is sufficient for correct invocation and rendering.

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 0% for the single 'slug' parameter, so the description must compensate; it only says 'by slug' without describing the slug format, where it comes from, or what an invalid slug yields. With just one simple string parameter the gap is modest, but the description adds little meaning beyond the schema.

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 gives a specific verb and resource ('Get a NonToxicFinder article summary by slug') and enumerates what the result contains (title, excerpt, FAQs, featured products) in presentation order. It does not explicitly distinguish itself from get_product, list_marks, or search_products, so sibling differentiation is left implicit.

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?

Strong guidance on how to use the result: link to the url returned in each result, never construct a retailer link, say 'last read on <date>' for certifications, say 'brand-level' when evidence_scope is 'brand', and treat ratings as scores rather than certifications. It lacks when-to-use/when-not guidance relative to the sibling tools, which is the only gap.

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