Skip to main content
Glama

WritersLogic business agents

id-kind

Identify an identifier's kind: UUID version, ULID, KSUID, snowflake, Stripe/GitHub/AWS prefix, EVM address, email, E.164 — Classifies up to 100 identifier strings by format and, where it can be read, decodes the embedded timestamp, for an agent that must not pass an id of the wrong kind to a payment, ledger or API call. Recognises UUID (RFC 9562 version and variant, nil and max), ULID, KSUID, Discord and Twitter snowflakes, EIP-55 EVM addresses (checksum verified), email (WHATWG syntax and RFC 5321 length limits), E.1

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": {
      "items": "<items>"
    },
    "name": "id-kind"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does add real behavioral detail beyond the name — checksum verification for EIP-55, RFC 9562 version/variant detection, timestamp decoding 'where it can be read', and a 100-item cap — but it does not describe the per-item result shape (kind, version, decoded timestamp, confidence) nor error/partial-failure behavior, and there is no output schema to fill that gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose, which is good, but the body is a long, dense enumeration with redundancy — UUID version is named in the opening clause and again spelled out in the format list, and the trailing list truncates mid-token. The supported-format catalogue earns its place for selection, but the duplication does not.

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

Completeness3/5

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

For a one-parameter classifier with no annotations and no output schema, the description covers what kinds are detected and some detection behavior, but leaves the return structure and the expect/pass-fail contract to the schema and the truncated tail. Adequate but not complete for an agent that must interpret results.

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?

Only one parameter family (items of {value, expect}). The description's enumeration of kinds maps onto the expect enum and thereby adds meaning, but the description text never explains the expect/pass-fail semantics or the value length bound — those live only in the schema. Useful overlap, but not compensating for the reported low schema coverage.

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?

States a specific verb and resource ('Identify an identifier's kind') and enumerates exactly which formats are recognised (UUID variants, ULID, KSUID, snowflakes, EVM address, email, E.164, vendor prefixes). An agent can tell this is a format-classification tool apart from siblings like checksum or tax-id-format without opening the schema.

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?

Gives a motivating context ('for an agent that must not pass an id of the wrong kind to a payment, ledger or API call'), which implies when to use it, but it never says when not to use it or names an alternative tool. Usage is implied rather than routed.

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