Skip to main content
Glama

GuideDoc Documentary Database

Search published GuideDoc articles

search_articles
Read-only

Find published documentary articles. Scheduled posts and private previews are excluded.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo
queryNo
languageNoen

Output Schema

NameRequiredDescriptionDefault
dataYes
sourceNoGuideDoc public documentary information; catalogue availability is not a playback entitlement

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / source / default
      Previous value: -"GuideDoc public information only; full films require an eligible subscription and territory"New value: +"GuideDoc public documentary information; catalogue availability is not a playback entitlement"
  2. Changed2 schema fields changed
    • addedInput schema / properties / language / const
      Added value: +"en"
    • removedInput schema / properties / language / enum
      Removed value: -[
      -  "en",
      -  "ca",
      -  "es"
      -]
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  4. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the useful behavioral detail that drafts, scheduled posts and private previews are omitted from results, but says nothing about result ordering, pagination behavior beyond the schema constraints, or rate/auth considerations.

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?

Two short sentences with zero filler, and the scope restriction is front-loaded immediately after the purpose. It is arguably under-sized rather than padded, so conciseness itself is a strength here.

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

Completeness2/5

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

An output schema and annotations exist, so return values and safety need not be restated. However, for a four-parameter search tool with no schema descriptions, the definition omits how matching works, what the degenerate empty-query case does, and how this differs from sibling search tools, leaving real gaps for an agent choosing between them.

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

Parameters2/5

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

Schema description coverage is 0% across all four parameters, so the description carries the burden of explaining them and does not: it never clarifies what `query` matches (title, body, tags), what an empty query returns, or how `page`/`limit` interact with the modest maximums of 50 pages and 20 per page. The only parameter-related hint is the word "published", which does not map to any listed field.

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 ("Find published documentary articles") plus a scope boundary (published only, scheduled posts and private previews excluded). It separates the tool from mutation or preview siblings, though it never names the closest alternative such as search_documentaries or get_article, so differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

Usage is implied by the exclusion clause, which tells the agent this is a discovery tool over publicly visible content only. There is no explicit guidance on when to prefer this over the generic `search` or `search_documentaries` siblings, and no pointer to get_article for fetching a specific article's full content.

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