Skip to main content
Glama

Get connections

renoir_get_connections
Read-onlyIdempotent

Every connection touching an entity, in both directions: credits, scores and influences. Each names both ends by id, carries the other end's title and year, and reads as a sentence. Up to 200 per page, crew before cast; total, more and offset page through the rest.

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": {
      "id": "<id>"
    },
    "name": "renoir_get_connections"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe entity whose neighbors to list.
typeNoOnly connections of this type.
offsetNoConnections to skip, for the next page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely new operational context not in the annotations: a hard cap of 200 per page, a 'crew before cast' ordering rule, and the fact that total/more/offset drive paging. It does not explain error behavior for an unknown id, keeping it below 5.

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?

Three sentences with no filler, and the core behavior (bidirectional connections on an entity) is front-loaded before return shape and pagination details. Phrasing like 'reads as a sentence' is slightly oblique but still conveys that each result is a human-readable string.

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 no output schema, the description carries the return-shape burden and does so reasonably: both ends named by id, the other end's title and year, page size, ordering, and pagination fields. It leaves gaps only around filtering behavior when 'type' is supplied and what happens for an invalid id, which are minor for a read-only traversal tool.

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 all three parameters are already documented, including the enum of connection types. The description supplements this only lightly — 'total, more and offset page through the rest' clarifies offset's role and 'credits, scores and influences' loosely maps to the enum — which is the baseline 3 for a schema that does the heavy lifting.

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 states a specific resource and scope: 'Every connection touching an entity, in both directions: credits, scores and influences.' An agent can immediately tell this traverses relationships rather than fetching the entity itself, which separates it from renoir_get_entity and renoir_get_film. It stops short of naming those siblings explicitly, so a 4 rather than 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?

Usage is implied by the phrase 'touching an entity' — you need an entity id to call it — but there is no explicit statement of when to prefer this over renoir_get_entity or renoir_search, nor any exclusion conditions. An agent must infer the routing decision from the resource names.

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