Skip to main content
Glama

About INDICIA DESK and this server

about_indicia
Read-onlyIdempotent

What INDICIA DESK is, what each tool returns, data freshness, what is deliberately not available here, plans, and the services (morning letter, idea check, channel audit, Whale Watch).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "about_indicia"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
linkYes
as_ofYesUTC time the underlying data was computed.
staleYesTrue when the data is older than its normal refresh cycle.
caveatNo
sourceNo
summaryYes
age_hoursNoHours between as_of and the time of this answer.
disclaimerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / age_hours
      Added value: +{
      +  "description": "Hours between as_of and the time of this answer.",
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered without the description. The description does add one genuinely useful behavioral note — that the content includes what is deliberately not available here, plus data freshness, both of which matter for an agent deciding how much to trust other tools. It stops short of saying whether the content is static or generated per call, or how large the payload is.

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

Conciseness4/5

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

A single sentence that front-loads the core topic ('What INDICIA DESK is') and then lists the supporting coverage areas efficiently. No filler or marketing prose. The compressed parenthetical service list is slightly dense but still scannable.

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?

With zero parameters and an output schema present, the description does not need to explain return values, and it correctly focuses on scope coverage instead. The main residual gap is operational: nothing tells the agent to call this first or how the content relates to the other tools' behavior. For a parameterless documentation endpoint, that is a minor omission rather than a blocking one.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline applies. The empty schema with additionalProperties=false is fully consistent with the description's implication of a simple parameterless lookup.

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 enumerates the specific contents the tool surfaces: what INDICIA DESK is, per-tool return values, data freshness, deliberately excluded data, plans, and named services (morning letter, idea check, channel audit, Whale Watch). This makes clear it is a documentation/onboarding resource rather than a data operation, distinguishing it from functional siblings like decision_journal or market_state. It lacks a crisp verb ('Describes...' / 'Returns an overview of...'), which keeps it short of a 5.

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?

The content list implies the tool is for orientation and orientation only, but the description never states when to call it — e.g., 'call this once at the start of a session' or 'use this instead of asking the user about the service.' No exclusions or alternatives are named. Usage must be inferred from the topic list alone.

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