Skip to main content
Glama
Sign In
signs-of-ai

signs-of-ai

by peopleworks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

extract_distinctive_phrases

Read-only

Extract distinctive phrases from document text and get ready-made exact-phrase search links for Google, Bing, and DuckDuckGo to verify suspicious phrasing.

Instructions

Extracts the most DISTINCTIVE phrases from a document — long, specific, proper-noun- or number-bearing wording most worth checking on the web — and returns each with ready-made exact-phrase search links (Google, Bing, DuckDuckGo). It does NOT search the web itself; it hands you the searches to run. Offline.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "extract_distinctive_phrases"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe document text.
maxPhrasesNoMaximum phrases to return. Default 8.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.5/5.0
Behavior4/5

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

With readOnlyHint provided, the description adds valuable context: it is offline, does not search the web, and returns ready-made search links. This goes beyond the annotation without contradicting it.

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?

The description is three concise sentences, front-loaded with the main action, and the negative clarification is compact. Every sentence earns its place.

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

Completeness5/5

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

For a two-parameter, read-only extraction tool, the description fully covers purpose, output format (search links), and behavioral constraints (offline, no searching). No output schema is needed as the output is described in prose.

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 coverage is 100% with descriptions for text and maxPhrases. The tool description does not add extra parameter semantics, so a baseline 3 is appropriate.

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

Purpose5/5

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

The description clearly states the tool 'Extracts' the specific resource 'DIStinctive phrases from a document' and defines what makes them distinctive. It also distinguishes itself from web-searching siblings by explicitly noting it does not search the web.

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

Usage Guidelines5/5

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

It explicitly states when to use the tool (to get phrases worth checking on the web) and when not to use it (it does NOT search the web itself). The note 'Offline' further clarifies the operating context, preventing misuse.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools