Skip to main content
Glama

Extract people, places, dates and contacts from text

entities
Read-only

Named entities in a text or a page: people, organisations, places, dates and money amounts (from the chat model), plus e-mail addresses, URLs and phone numbers (from patterns), each de-duplicated with a count. With url, the page's readable text is used (robots.txt is respected). Price: $0.003 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
urlNoOr a page address, https://…
textNoText, up to 12,000 characters

Output Schema

NameRequiredDescriptionDefault
urlNo
urlsNo
datesNo
modelNo
moneyNo
emailsNo
peopleNo
phonesNo
placesNo
sourceNo
checkedAtNo
organisationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing provenance per entity type (model vs pattern matching), de-duplication with counts, that robots.txt is honoured when fetching a page, the exact price ($0.003 per successful call) with the payment network, and that failed calls are not charged. This is the kind of cost and side-effect detail an agent cannot infer from structured fields.

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?

A single dense paragraph with the entity enumeration front-loaded and no filler, though the price and robots.txt clauses sit inside the same block and would scan better as separate sentences.

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?

An output schema exists, so the description needn't explain return values, yet it still hints at the count field. With two optional parameters and no required ones, the only gap is what happens if neither url nor text is supplied.

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 description coverage is 100%, so both parameters are already documented, and the description adds only the behavioural link between url and readable-text extraction. It does not say whether both parameters may be combined, and the 12,000-character limit lives in the schema rather than the description.

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?

Names the exact resource (named entities) and enumerates the extractable types, splitting them by source: people/organisations/places/dates/money come from the chat model, while e-mail/URL/phone come from patterns. It also states the output shape (de-duplicated with a count). It does not distinguish itself from near-siblings such as extract, contacts or phone, so it stops short of 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 Guidelines3/5

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

Usage is implied by the two input modes: pass raw text, or pass a url and the page's readable text is used instead. That gives conditional guidance on which parameter to pick, but there is no explicit when-to-use/when-not statement and no alternative tool is named.

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