Skip to main content
Glama
Sign In
hlido-mcp

hlido-mcp

by ankitkapur1992-hlido
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

get_behavioral_trace

Fetch behavioral evaluation trace for a Hlido-reviewed agent, including per-task pass/fail, adapter, behavioral tier, and signed trace link. Use to verify independent test results beyond marketing claims.

Instructions

Fetch the behavioral evaluation trace for a Hlido-reviewed agent — per-task pass/fail, adapter used, behavioral tier, and signed trace link. Returns status 'not_yet_bench_tested' if the slug hasn't been evaluated yet, or 'not_testable' if the agent's interface doesn't support automated bench runs. Use this when you need evidence that an agent's coding/task behaviour has been independently verified beyond marketing claims.

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": {
      "slug": "<slug>"
    },
    "name": "get_behavioral_trace"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe Hlido slug to fetch behavioral trace for (e.g. 'aider', 'opencode')
spec_versionNoBehavioral spec version (default 'v0.1'). Omit to get the latest available.v0.1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full transparency burden. It discloses that the tool can return statuses like 'not_yet_bench_tested' and 'not_testable', and describes the data contained in the trace. This gives meaningful insight into the tool's behavior and limitations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two concise sentences, front-loaded with the core action and content. Every sentence contributes useful information without redundancy or fluff.

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 simple 2-parameter fetch tool with no output schema, the description covers the purpose, usage context, possible return statuses, and the key contents of the trace. It is comprehensive enough for an agent to decide when to invoke it and interpret basic responses, though a bit more detail on the signed link format could be added.

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 coverage is 100%, and the description adds no new parameter-specific meaning beyond the schema. The schema already documents 'slug' and 'spec_version' with examples and default behavior, so the description offers no additional semantic value for parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Fetch') and the specific resource ('behavioral evaluation trace for a Hlido-reviewed agent'), and lists the trace contents (per-task pass/fail, adapter, tier, signed link). This distinguishes it from sibling tools like get_scorecard or get_incidents.

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?

The description provides an explicit use case: 'Use this when you need evidence that an agent's coding/task behaviour has been independently verified beyond marketing claims.' It also mentions edge cases (not_yet_bench_tested, not_testable) but does not explicitly name alternatives or when-not conditions, so it falls slightly short of a 5.

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