Skip to main content
Glama

Nicolas Sitter Research

get_article

Read-only

Fetch one research article by its URL slug — the last path segment of a /research/ URL. Use this after search_research_articles to read a specific study, or when the user names an article or pastes one of its URLs. format 'summary' (the default) returns headline, description, date and read time; format 'full' also returns the complete article body as markdown, which is what you want if the user asks about the methodology, the numbers, or what the study actually found.

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
slugYesArticle slug, e.g. "ai-hotel-landscape-2026".
clientNoOptional: identify yourself, e.g. "my-agent/1.0". Not required and never used by the tool itself — recorded only so the public tracker at /projects/agent-tools can measure how many callers self-identify when nothing forces them to.
formatNo'summary' (default) or 'full'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real value beyond that by disclosing what each format returns (headline, description, date, read time vs. full body as markdown) and by openly characterizing the 'client' parameter as inert telemetry. It does not say what happens when a slug is unknown, which keeps it off 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?

Purpose and slug derivation are front-loaded, then alternatives, then format semantics — a sensible order with no filler. The format sentence is long and clause-heavy, but each clause carries a distinct decision rule, so the length is earned rather than padding.

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 read-only single-record fetch with no output schema, the description supplies return-field expectations for both formats and a clear call trigger, which is what an agent needs to invoke it correctly. The remaining gap is failure behavior for an invalid or non-existent slug, which is left entirely unaddressed.

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 coverage is 100%, so the baseline is 3, but the description goes beyond the enum's bare "'summary' (default) or 'full'" by mapping user intent (methodology, numbers, findings) to the 'full' choice. It also explains the slug's provenance rather than just restating the field name, adding meaning the schema does not carry.

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?

States a specific verb and resource — fetch one research article — and pins down the identifier format as "the last path segment of a /research/<slug> URL." It distinguishes itself from search_research_articles by framing this as the follow-up read step, so an agent can route without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit triggers are given: after a search, when the user names an article, or when a URL is pasted. It also names the alternative (search_research_articles) and the condition that selects it, plus a decision rule for 'full' when the user asks about methodology, numbers, or findings.

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