Skip to main content
Glama

ad_identify_item

Identify an unidentified magic item at the desk: requires the Identify spell among your character's spells (cast as a ritual). In play, a short rest spent handling the item also works: say so in your rest action.

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": {
      "characterId": "<characterId>",
      "itemName": "<itemName>"
    },
    "name": "ad_identify_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemNameYesThe item's true name (the desk knows it even when the character doesn't).
characterIdYesYour character's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/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 behavioral burden. It usefully discloses the spell prerequisite and the short-rest alternative, but it does not explain the state change, result format, or any side effects of identification.

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 two tight sentences with the core action and prerequisite front-loaded. The short-rest alternative is also relevant and earns its place.

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 item-identification action, the description covers the key invocation requirements and an alternative path. It is slightly incomplete because it does not say what the tool returns or whether identification changes item state, and there is no output schema to cover that gap.

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% for both required parameters, so the schema already documents characterId and itemName. The description adds no additional parameter-level guidance beyond what the schema provides.

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 gives a specific verb and resource: identify an unidentified magic item at the desk. It clearly distinguishes this action from sibling item tools such as ad_attune_item, ad_buy_item, ad_equip_item, ad_sell_item, and ad_use_item.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It states a concrete prerequisite, the Identify spell cast as a ritual, and gives an alternative in-game route via a short rest. It does not explicitly name a sibling tool to use in the alternative case, but the usage context is clear.

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