Skip to main content
Glama

Kiltikonet (public)

Lens — cartes culturelles interopérables

lens_cultural_context
Read-onlyIdempotent

Cartes textuelles vérifiées pour un client XR ; aucune caméra, position ni commande matériel.

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": {
      "territory": "<territory>"
    },
    "name": "lens_cultural_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
territoryYes

Output Schema

NameRequiredDescriptionDefault
cardsNo
territoryYes
data_limitsNo
generated_atYes
content_sourceYes
actions_executedNo
personal_location_inferredNo
device_capabilities_claimedNo
requires_user_activation_for_xrNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.2/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful privacy/scope context by stating that it involves no camera, position, or hardware commands, but it does not explain what 'verified textual cards' means operationally or how results are produced.

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

Conciseness3/5

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

The description is a single efficient sentence with no filler, but its brevity comes at the cost of under-specification rather than purposeful conciseness.

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?

The presence of an output schema and annotations relieves some burden, but for a tool requiring a territory and supporting a limit, the description omits nearly all essential context about inputs, scope, and intended use.

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?

Schema description coverage is 0% for both parameters, so the description must explain 'territory' and 'limit'. It provides no information about either parameter, leaving their meaning and expected values entirely undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says it provides 'verified textual cards for an XR client' but never states the action or resource clearly enough to distinguish it from siblings such as observatory_regional_lenses. It names constraints (no camera, position, or hardware command) rather than defining what lens_cultural_context actually does.

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 many observatory_* and culture_* siblings. No alternatives, prerequisites, or exclusion conditions are mentioned.

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