Skip to main content
Glama

Lattice

by io.namiq
OverviewDiscussionsAdmin

Get licence notices

graph_notices
Read-onlyIdempotent

Return the licence and attribution notices for the data sources behind an answer.

    Other tools list notice ids with their answers. Pass those ids here to get, for each notice, its title, what it applies to, the obligation it places on you (for example attribution wording or a share-alike condition) and the notice text. Long texts are cut and flagged text_truncated, with text_url pointing to the full text.

    When to call it: before you quote, republish or build on anything the graph returned, and then quote what the obligation requires. Unknown ids are reported in unknown rather than failing.

    What it is not for: it returns no security facts, and it is source licence information, not legal advice. It only reads and gives the same answer each time for a snapshot.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoNotice ids to fetch, as listed in the notice list of other answers, at most 10 per call. Omit to get the notices the server holds (up to 10). Ids it does not know come back in the unknown list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / ids / description
      Added value: +"Notice ids to fetch, as listed in the notice list of other answers, at most 10 per call. Omit to get the notices the server holds (up to 10). Ids it does not know come back in the unknown list."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, it discloses truncation behavior (long texts cut, flagged text_truncated, text_url for the full text), the graceful handling of unknown ids (reported in unknown rather than failing), and deterministic snapshot reads. These are exactly the behaviours an agent cannot infer from annotations.

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?

Well front-loaded: the core action leads, then call timing, then exclusions. The "What it is not for" paragraph is slightly padded with the legal-advice caveat, but every part still carries selection-relevant information.

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?

With no output schema, the description carries the full burden and delivers: it enumerates the returned fields (title, what it applies to, the obligation, the notice text) and the truncation metadata. Nothing needed to call or interpret the tool correctly is missing.

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 100%, so the ids parameter, the 10-per-call cap and the unknown-id behaviour are already documented in the schema. The description adds a little framing (ids come from other answers) but largely restates the schema, so baseline 3 is appropriate.

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?

States a specific verb and resource ("Return the licence and attribution notices for the data sources behind an answer") and explicitly positions itself against the other graph_* siblings by noting that they list notice ids while this tool resolves them. An agent can select it without opening any 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?

Gives an explicit trigger ("before you quote, republish or build on anything the graph returned") and explicit non-uses ("returns no security facts", "not legal advice"). It also documents the intended call chain from the notice ids emitted by other tools, which is the key routing fact.

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

All Lattice 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