Skip to main content
Glama

ecosystem_mark_as_reference

Mark a reviewed repository as an architectural reference and advance it to referenced status, so future searches flag it as already researched and the team avoids redundant deep scans.

Instructions

Stage 3 reference path — add lifecycle:reference tag + advance to referenced.

Use when the debate concludes that the repo is worth keeping as an architectural reference but not integrated. The repo will appear highlighted in future searches as "already researched" so the team avoids re-deep-scanning it.

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": {
      "deep_review_id": "<deep_review_id>"
    },
    "name": "ecosystem_mark_as_reference"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idNoOptional agent identifier recorded on the tag.
confidenceNo0.0-1.0; default 1.0 (manual decision).
deep_review_idYesTarget deep_review row id.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.2

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the concrete side effects (tag added, status advanced to 'referenced') and a downstream consequence (repo gets highlighted as 'already researched' in future searches, discouraging re-scanning). It omits idempotency and whether an existing tag/status is overwritten, which matters for a state-mutating tool.

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?

The action and the resulting state change are front-loaded in the first sentence, and the second sentence explains the rationale and downstream effect. Slightly verbose markup and an extra concrete-effect clause keep it from being maximally tight.

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?

An output schema exists, so return values need not be explained, and the description covers the prerequisites, the state transition, and the visible after-effect. Only edge behavior such as idempotency or what happens on an already-referenced repo 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 all three parameters (deep_review_id, agent_id, confidence) are already documented in the schema. The description adds no information about parameter meaning or acceptable ranges, so the baseline of 3 applies.

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 names a specific mutation verb pair ('add lifecycle:reference tag' plus 'advance to referenced') and situates it as 'Stage 3' of a pipeline, so an agent can tell exactly what state change happens. It does not explicitly contrast itself with neighboring stage tools such as ecosystem_apply_debate_result, so it stops short of full sibling differentiation.

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

Usage Guidelines4/5

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

It gives a clear triggering condition: use when the debate concludes the repo is worth keeping as a reference but not integrating. The implied alternative (integration) is stated in prose but no sibling tool name is given, leaving the agent to infer which tool handles the integrate path.

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