Skip to main content
Glama
Sign In
ariadne

ariadne

by whyy9527
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

rate_result

Record whether results helped locate files or understand dependencies. Provide feedback after query_chains or expand_node to improve future searches.

Instructions

Record whether Ariadne results were useful. Call this after using query_chains or expand_node to log feedback for future improvement. If node_ids is omitted after a recent query_chains call, Ariadne infers node_ids from hint + cluster_rank. Feedback is stored locally in feedback.db and survives DB rebuilds.

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": {
      "hint": "<hint>",
      "accepted": "<accepted>"
    },
    "name": "rate_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
hintYesThe hint used in query_chains or the node name used in expand_node
acceptedYestrue if results helped locate files or understand the chain; false if irrelevant or misleading
node_idsNoNode IDs from the result that were actually useful
cluster_rankNoWhich cluster was referenced (1-based). Use 0 for expand_node results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.7

TDQS

A4.6/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 burden. It reveals that feedback is stored locally in feedback.db and survives DB rebuilds, and explains inference behavior. No side effects or permission needs are mentioned, but overall transparent enough.

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 concise, front-loaded with purpose and usage, then provides details about inference and storage. Every sentence adds value without redundancy.

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?

Given the low complexity and no output schema, the description is complete enough. It explains behavior, parameters, and storage. Minor gap: no return value description, but not critical for a feedback 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?

Schema coverage is 100%, but the description adds meaning: explains that node_ids can be inferred from hint and cluster_rank if omitted, and clarifies cluster_rank usage (0 for expand_node). This adds value beyond the schema.

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 tool's purpose ('Record whether Ariadne results were useful') and distinguishes it from siblings by specifying it is used after query_chains or expand_node.

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

Usage Guidelines5/5

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

The description explicitly says when to call this tool ('after using query_chains or expand_node') and explains inference behavior when node_ids is omitted, providing clear usage context.

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