Skip to main content
Glama

Noticeboard search

noticeboard_search
Read-onlyIdempotent

Live posts on the borough's noticeboard (for sale, free, wanted, local help).

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

Input Schema

NameRequiredDescriptionDefault
qNowords to match
areaNowhere: a London borough (e.g. ealing, brent, hounslow) or a postcode district (e.g. W7, UB1)
limitNohow many (default 5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety and side-effect profile is covered. The description adds one useful behavioral fact — results are "live" posts, implying only currently active listings rather than historical/expired ones — but says nothing about result ordering, pagination beyond the schema's limit, or coverage boundaries of the dataset.

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 with the content scope front-loaded and zero filler. It is efficient, though its brevity edges into under-specification rather than crisp precision.

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?

With three optional parameters, a fully documented schema, and no output schema, the description is minimally adequate. It never indicates what a returned post looks like or whether empty results are common, which is the main gap for a search tool with no declared response shape.

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%, with q, area, and limit all documented including examples and the default of 5, so the schema carries parameter meaning fully. The description adds no syntax, matching behavior (e.g. whether q is free text or AND/OR), or guidance on combining q with area, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource ("posts on the borough's noticeboard") and the listing categories (for sale, free, wanted, local help), which helps an agent understand the content domain. However, it never states the action — the search/retrieve verb exists only in the tool name — and it does not distinguish this from siblings such as search_businesses or area_now.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of alternatives, and no prerequisites. An agent deciding between noticeboard_search, search_businesses, and events_on gets no routing signal from the description at all.

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