Skip to main content
Glama

Earlier searches to exclude

list_exclusion_sources
Read-onlyIdempotent

The user's earlier searches whose people can be left out of a new one (exclude_tasks of create_search): all analysed or only the leads. [REST: GET /api/exclusions/sources]

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without prose. The description adds the REST endpoint and the 'all analysed or only the leads' distinction, but that clause is ambiguous — it is unclear whether it describes a filter (there are no parameters), a response grouping, or the notion of exclusion coverage, so it adds uncertainty as much as context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single sentence, which is appropriately sized, but the core purpose is buried in a relative clause ('whose people can be left out of a new one') and the parenthetical plus REST annotation fragment the flow. The trailing 'all analysed or only the leads' is elliptical and reads as an unfinished thought.

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 no parameters and no output schema, the description carries the full burden of explaining what comes back, and it does not: the 'all analysed or only the leads' clause gestures at the result content without clarifying what fields or categories the caller should expect. It does establish how the returned searches feed into create_search, which is the essential connective context.

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?

The tool takes zero parameters and the schema is an empty object, so there is nothing for the description to disambiguate. The baseline for a parameterless tool applies; the description correctly does not invent parameter semantics.

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 concrete resource (the user's earlier searches that can act as exclusion sources) and ties it to a specific consuming field, exclude_tasks of create_search. That distinguishes it from list_searches, which has no such exclusion framing. The phrasing 'whose people can be left out of a new one' is convoluted, which keeps it below a 5.

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

Usage Guidelines4/5

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

Usage is clearly implied by the explicit link to exclude_tasks of create_search: an agent should call this when deciding which prior searches to exclude from a new search. No when-not condition or prerequisite ordering is stated, so it stops short of full routing guidance.

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