Skip to main content
Glama

Lookup structured RedM discoveries and their relationships

discovery_lookup
Read-only

Look up complete structured RedM discoveries records: animation dictionary + clip, audio bank/soundset + sound, IMAP hash + coordinates, clothing items and wearable states, particle dictionary + effect, named flags, and textures with image links. Use for literal identifiers even deep inside the largest Lua tables. Pass name for exact member lookup, parent for exact dictionary/bank/group, search for keywords or a partial identifier, or hash for a 32-bit hex/decimal hash. Optional kind restricts domain; near finds IMAPs in a 3D radius. Returns complete records with source commit and line range; path discovery: can be opened with get_document. Paginate using returned nextOffset. For ped/weapon/object/door/vehicle model lookup use asset_lookup; for callable 64-bit natives use lookup_native; for behavior explanations use semantic_search. Examples: {kind:'animation',name:'ig2_jobbriefs_handover_p_woodstake01x'}, {kind:'animation',search:'piano'}, {kind:'imap',name:'bone_05'}, {kind:'wearable',name:'CLOTHING_ITEM_F_BOOTS_017_TINT_002'}. RedM only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hashNo32-bit hex, unsigned decimal, or signed decimal hash.
kindNo
nameNoExact clip, sound, IMAP, item, flag or texture name; case-insensitive.
nearNo
limitNo
offsetNo
parentNoExact dictionary, audio bank/soundset, or returned parent group.
searchNoKeywords or partial identifier, e.g. piano, volcano, SHORT_PANTS.
namespaceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hintYes
statusYes
recordsYes
truncatedYes
nextOffsetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

Read-only behavior is already covered by annotations, and the description adds useful details: complete records with source commit and line range, pagination via nextOffset, near searches restricted to IMAPs, and the discovery:<id> path for get_document. This goes meaningfully beyond the 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.

Conciseness5/5

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

The description is long but dense and well ordered: purpose first, then parameter semantics, return behavior, pagination, sibling routing, and examples. Every sentence contributes operational value, with no filler.

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

Completeness5/5

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

Given 9 optional parameters, an output schema, and readOnly annotations, the description covers input modes, result contents, pagination, related-tool routing, and the RedM-only scope. Nothing an agent needs to invoke or disambiguate this tool is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is low at 44%, but the description compensates well by explaining name as exact member lookup, parent as exact dictionary/bank/group, search as partial/keyword, hash as 32-bit hex/decimal, kind as domain restriction, and near as a 3D IMAP radius. Only namespace and basic pagination parameters are left to the schema.

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 opens with a specific lookup verb and enumerates the exact record families it handles: animations, audio, IMAPs, clothing, wearables, particles, flags, and textures. It also distinguishes itself from asset_lookup, lookup_native, and semantic_search, so an agent can identify this tool 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 Guidelines5/5

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

It explicitly says to use this for literal identifiers even inside large Lua tables and names sibling alternatives for model lookups, 64-bit natives, and behavior explanations. The per-parameter usage rules and concrete examples give clear triggering conditions.

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.