Skip to main content
Glama

Semantic map of the collection

get_semantic_map
Read-onlyIdempotent

The collection as unnamed groups of records close in meaning (k-means over EmbeddingGemma 2 vectors): size, type mix, top subjects, countries and projects, records nearest the centre. group lists one; id finds a record's group.

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": "get_semantic_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoA record (omeka_id or typed id): its group
groupNoA group id: list its records, nearest the centre first
limitNoGroups (default 10, max 30) or records (default 20, max 100)
typesNoWith group/id: only these record types
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered by structured data. The description adds meaningful behavior by disclosing the clustering algorithm and the exact composition of each group's summary. It does not discuss auth needs, rate limits, or refresh/staleness behavior of the computed map, so credit beyond the baseline is moderate.

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?

It is a single compact sentence with the resource and clustering method front-loaded, followed by the output inventory and the two mode hints. The parenthetical and clause stack are dense but each element earns its place; only minor tightening would improve it.

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?

For a 5-parameter, all-optional, read-only tool with no output schema, the description covers what the map contains and how to select a group or a record's group. Remaining gaps, such as how types interacts with group/id and whether the map is recomputed or cached, are minor given the annotations already establish the safety profile.

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 high (80%), so the schema already documents id, group, limit, types and offset. The description restates the `group`/`id` semantics and clarifies the output fields, but adds little about `types` filtering or offset paging beyond what the schema says. Baseline 3 is appropriate.

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 gives a specific resource (the collection) and an explicit method (k-means over EmbeddingGemma 2 vectors) producing unnamed semantic groups, and it enumerates what each group contains (size, type mix, top subjects, countries, projects, nearest records). An agent can grasp the tool's output without opening the schema. It stops short of naming a sibling such as get_fulltext_map or list_groups, so the contrast with those alternatives remains implicit.

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 line '`group` lists one; `id` finds a record's group' tells the agent the two invocation modes, implying when to browse groups vs when to locate a record's group. However, there is no explicit when-to-use or when-not guidance relative to siblings, and no prerequisites or cost caveats are stated.

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.