Skip to main content
Glama
Sign In
TEOS Agent Tools

TEOS Agent Tools

by threebeats
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

extract_keyphrases

Identify key phrases and core theme from any text to capture its meaning. Use for summarizing, analysis, or content insights.

Instructions

Give any text; get the key phrases that carry its meaning and the core theme. Paid. Returns keyphrases, theme.

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

Input Schema

NameRequiredDescriptionDefault
textYesText to extract keyphrases from

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It discloses that the operation is paid and names the return fields (keyphrases, theme), but omits details such as cost amount, input size limits, or processing constraints.

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?

The description is short and front-loaded, with no wasted sentences. The telegraphic style ('Paid. Returns keyphrases, theme.') is efficient but slightly fragmentary.

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 one-parameter extraction tool with no output schema, the description adequately names the return fields and notes the paid nature. It is complete enough for invocation, though additional details on output structure or limits would strengthen it.

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?

There is only one parameter, and the schema already documents it fully with 100% description coverage. The description's phrase 'Give any text' adds minor clarity but no syntax or format constraints beyond the schema.

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 uses specific verbs and resources: extract key phrases and core theme from text. It is clear what the tool does, though it does not explicitly distinguish itself from siblings such as summarize_url or clean_data.

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?

'Give any text' implies the input expectation, and 'Paid' signals a cost consideration. However, there is no explicit guidance on when to choose this over alternatives or any exclusions.

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