Skip to main content
Glama
Sign In
eds-mcp-server

eds-mcp-server

by Edwson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Get the agent protocol

get_agent_protocol

Retrieve the seven-step read path and hard rules that govern agent access to design tokens and component contracts, blocking builds when rules are violated.

Instructions

The consumer system's machine-carried reading logic: the seven-step read path (discover → fetch index → select → read register → resolve bundles & hard rules → build from tokens → gate to a human) plus the hard rules that can BLOCK a build.

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_agent_protocol"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.17.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only describes the content returned. It does not disclose whether the tool has side effects, requires authentication, or is safe to call repeatedly. The mention of 'reading logic' hints at idempotency but is not explicit.

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 description is a single sentence that front-loads the main purpose. It is concise but uses jargon ('gate to a human'), which slightly reduces clarity. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and no annotations, the description adequately conveys what the protocol includes (steps and rules) but lacks details on output format, representation, or meaning of terms like 'hard rules'. It is minimally complete for a no-parameter tool.

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

Parameters4/5

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

The tool has zero parameters, so baseline score is 4 per instructions. There is no parameter information to add, and the schema coverage is 100% by definition.

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 it returns the consumer system's read protocol, including a 7-step read path and hard rules. It clearly identifies what the tool retrieves, distinguishing it from sibling tools that deal with tokens, components, or bundles.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives, such as when to retrieve token groups or components instead. The description lacks context for appropriate usage scenarios.

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