Skip to main content
Glama

Ultralayer

by io.github.UltralayerHQ
OverviewDiscussionsAdmin

List Guidance

list_guidance
Read-only

Forward-looking guidance issued by public companies, grouped into series with revision history.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNotimestamp: recently updated; guided_period_end: period date; comparable: strongest like-for-like number in the match set; revision_delta: largest midpoint move.timestamp
limitNo
detailNoessential:quotes; standard:citable; full:all.full
symbolsNoMatch any.
segmentsNoMatch any. 'null' is consolidated.
metric_keysNoMatch any.
values_modeNoall: revision history, newest first; latest: newest observation only.all
metric_basisNoMatch any.
source_typesNoMatch any. Document class the observation was read from.
end_timestampNoSystem timestamp; Inclusive ISO 8601; null=realtime
start_timestampNoSystem timestamp; Inclusive ISO 8601
guided_fiscal_yearNo
guided_period_typeNoMatch any.
revision_directionNoMatch any; latest observation only.
guided_period_end_toNoInclusive guided period-end date.
guided_fiscal_quarterNo
guided_period_end_fromNoInclusive guided period-end date.
metric_key_exact_matchNotrue: exact metric_keys, case-insensitive; false: case-insensitive substring. Ignored without metric_keys.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / source_types / anyOf
      Previous value: -[
-  {
-    "items": {
-      "enum": [
-        "earnings_release",
-        "guidance_update",
-        "earnings_call"
-      ],
-      "type": "string"
-    },
-    "maxItems": 3,
-    "minItems": 1,
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "enum": [
+        "earnings_release",
+        "guidance_update",
+        "interim_update",
+        "earnings_call"
+      ],
+      "type": "string"
+    },
+    "maxItems": 3,
+    "minItems": 1,
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations (readOnlyHint=true, destructiveHint=false) already declare the read-only safety profile. The description adds one behavioral trait: output is 'grouped into series with revision history,' which is useful but limited. It does not mention sorting defaults, pagination, or how revision history is represented.

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?

A single, front-loaded sentence with no redundant words. It conveys the core purpose and the key behavioral nuance (grouping and revision history) efficiently.

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

Completeness2/5

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

For a tool with 18 parameters and no output schema, the description is too terse. It lacks an explanation of the returned structure, what 'series' means in practice, and how to interpret revision history. An agent would need to infer much from parameter names and examples.

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 83%, so the schema itself documents most parameters (e.g., sort meanings, detail levels, filters). The description adds no parameter-level context beyond what the schema provides, aligning with the baseline for high coverage.

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?

The description identifies a specific verb ('list') and resource ('forward-looking guidance issued by public companies'), and adds distinguishing detail ('grouped into series with revision history'). It is clear but does not explicitly contrast with siblings like list_guidance_outcomes, so it doesn't fully differentiate within the tool family.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus the alternatives (e.g., list_guidance_outcomes, search_developments, list_wire). The description only states what it does without any 'use this when...' context or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Ultralayer toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources