Skip to main content
Glama

Tools for Agents

by io.github.max124vip-dev
OverviewDiscussionsAdmin

extract_phones

Extract phone numbers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesInput text

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / args
      Removed value: -{
-  "description": "Tool arguments",
-  "properties": {
-    "text": {
-      "description": "Primary input text",
-      "type": "string"
-    }
-  },
-  "type": "object"
-}
    • addedInput schema / properties / text
      Added value: +{
+  "description": "Input text",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[]New value: +[
+  "text"
+]
  2. Added

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries full disclosure burden, but it only states the core function. It does not mention return format, handling of malformed numbers, or any behavioral traits beyond extraction.

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 concise with no filler, but it lacks structure or additional clarifying details. It's appropriately short for a simple tool, though somewhat under-specified.

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

Completeness2/5

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

For a tool with no annotations and no output schema, the description fails to convey what output to expect or edge cases. It's too brief to be fully contextual.

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% for the single 'text' parameter, so the schema fully documents the input. The description adds no additional parameter semantics, but 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?

The description uses a specific verb 'extract' and resource 'phone numbers', clearly stating the tool's function. However, it lacks context about input/output format or sibling differentiation, so it's clear but minimal.

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?

No guidance is provided on when to use this tool versus alternatives like validate_phone or extract_emails. The intended use is implied by the name but not explicitly stated.

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

All Tools for Agents toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources