Skip to main content
Glama

Search the blog

search_blog
Read-onlyIdempotent

Search published MotifyMe blog posts (UK car buying, selling, finance introductions, running costs, fuel, tax, MOT). Returns title, summary, category, date and url.

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

Input Schema

NameRequiredDescriptionDefault
limitNo1-20
queryNokeywords
categoryNoe.g. Driving, Fuel, Running Costs, MOT & Tax

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond that by scoping results to 'published' posts and enumerating the returned fields (title, summary, category, date, url), which matters because there is no output schema.

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 sentences, zero filler, with the resource and scope front-loaded and the return shape following. Every clause carries information an agent can act on.

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 simple read-only search with fully documented parameters, the definition covers purpose, scope and return fields, which compensates for the absent output schema. It could still say what happens with an empty query or how limit defaults, but nothing critical is missing.

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 limit, query and category are already documented in the schema. The description adds no extra meaning such as default limit, matching behavior, or whether omitting query returns all posts, so the baseline 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?

States a specific verb (Search) and resource (published MotifyMe blog posts) and enumerates the topical scope, which lets an agent distinguish it from get_blog_post by the plural/search framing. It stops short of explicitly contrasting with the sibling that fetches a single post.

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 only implied: the word 'Search' plus the topic list suggests keyword lookup, but there is no statement of when to prefer this over get_blog_post or when not to use it. No prerequisites or exclusions are given.

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