Skip to main content
Glama

Search content

search_content
Read-onlyIdempotent

Search articles, news and opinion, or return the latest content.

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_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoSearch words. Leave out to get the latest content.
typeNoKind of editorial content: article, news or opinion.
limitNoNumber of results to return. Default 10, maximum 20.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Number of results to return. Default 10, maximum 20."
    • addedInput schema / properties / q / description
      Added value: +"Search words. Leave out to get the latest content."
    • addedInput schema / properties / type / description
      Added value: +"Kind of editorial content: article, news or opinion."
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered. The description adds one genuinely useful behavioral note — that omitting the query switches to a latest-content listing — but says nothing about result ordering, pagination, or coverage limits beyond what the schema states.

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 that front-loads the primary search behavior and appends the alternate mode. Nothing is redundant, though the phrasing 'articles, news and opinion' slightly duplicates the enum values already in the schema.

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 three-optional-parameter read tool with no output schema, the definition covers the essentials and annotations carry the safety context. It stops short of describing what results look like or how the two modes differ in output shape, which would have closed the remaining gap.

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 description coverage is 100%, so all three parameters (q, type, limit) are already documented including the default and maximum for limit. The description adds no meaning beyond the schema, so the baseline of 3 applies.

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 verb (search) and resource domain (articles, news, opinion) and also discloses a second mode: returning the latest content. It is clear enough to distinguish from a generic sibling, though it never contrasts itself with the similarly named 'search' or 'search_providers' tools.

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 'or return the latest content' clause, which signals the no-query browse mode, but that information is also in the schema. There is no explicit when-to-use-this-vs-alternative guidance and no exclusions, so the agent must infer routing from sibling names.

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