Skip to main content
Glama

Tools for Agents

by io.github.max124vip-dev
OverviewDiscussionsAdmin

entity_extract

Extract emails, URLs, phones, dates

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

B3.4/5.0
Behavior3/5

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

No annotations are present, so the description bears the full transparency burden. It clearly states the types of entities extracted, which is the core behavior, but it does not disclose output format, deduplication behavior, or handling of edge cases. This is a minimum-viable disclosure.

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 a single short sentence, front-loaded with the action verb and entity types. Every word adds value, with no redundant or filler content.

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?

The tool has no output schema, and the description does not explain the return format or any limitations. Given the tool's simplicity, the description is too minimal to be fully self-contained; the agent must infer the output structure.

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?

The schema already describes the sole parameter 'text' as 'Input text' with 100% coverage. The description adds no additional semantic information about the parameter, so the baseline 3 applies.

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 uses a specific verb 'Extract' and enumerates the entity types (emails, URLs, phones, dates), clearly defining the tool's scope. This differentiates it from single-type siblings like extract_emails and extract_url.

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 the many specialized extractors listed as siblings (e.g., extract_emails, extract_url). The context is implied by the listed entity types but no explicit alternatives or exclusions are given.

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