Skip to main content
Glama
Sign In
Semaphore UI MCP server

Semaphore UI MCP server

by johsem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_integration_matcher_references

Read-onlyIdempotent

Retrieves references for a specific integration matcher in a project, so you can inspect where that matcher is used.

Instructions

Get Integration Matcher Refs. GET /project/{project_id}/integrations/{integration_id}/matchers/{matcher_id}/refs.

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": {
      "project_id": "<project_id>",
      "integration_id": "<integration_id>",
      "matcher_id": "<matcher_id>"
    },
    "name": "get_integration_matcher_references"
  }
}

Input Schema

NameRequiredDescriptionDefault
matcher_idYes
project_idYes
integration_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: it does not explain what references are returned, whether the matcher must exist, or what an openWorld call implies here, so for a tool whose annotations leave the content opaque it under-delivers.

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?

It is two terse fragments with no filler, so it is not bloated. But brevity here is under-specification rather than efficiency, and the raw endpoint path is the only content-bearing element.

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?

For a 3-parameter tool with 0% schema description coverage and no output schema, the description should explain what references are and roughly what is returned. Instead it provides only the endpoint, leaving the agent unable to predict the response shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the three required integer parameters are undocumented in the schema. The URL template at least shows that project_id, integration_id, and matcher_id are path identifiers nested in a hierarchy, but it adds no constraints, formats, or meaning beyond that.

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 just restates the tool name ("Get Integration Matcher Refs") and appends the raw HTTP path. It never says what a "ref" is or what the response represents, so an agent cannot distinguish this from get_integration_references, get_integration_value_references, or get_integration_matcher without guessing from the path.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. The sibling list contains several closely related reference getters (get_integration_references, get_integration_value_references), and the description gives no basis for choosing among them.

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

Deploy Server

Other Tools