lookup_number
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| number | Yes | The angel number to look up (e.g. '111', '444') |
Angel Numbers Deterministic API
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
D1/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness1/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose1/5
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines1/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
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.
TDQS
D1.9/5.0
Disambiguation4/5
The tool names suggest distinct purposes: get_daily_number for today's number, lookup_number for querying a specific number, and interpret_sequence for analyzing sequences. Without descriptions, there is slight potential confusion between get_daily_number and lookup_number, but they appear to target different use cases.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in snake_case: get_daily_number, interpret_sequence, lookup_number. The naming is uniform and predictable.
Tool Count4/5
With 3 tools, the set is slightly small but reasonable for the domain of angel numbers. Each tool covers a distinct common operation: daily number, sequence interpretation, and number lookup. It feels appropriately scoped, though a few more tools could be useful.
Completeness3/5
The tools cover basic functionalities for angel numbers: getting a daily number, interpreting sequences, and looking up individual numbers. However, there are notable gaps such as lack of historical data, list of numbers, or more detailed interpretations. The surface is workable but incomplete for a comprehensive numerology API.