Skip to main content
Glama

ThinkNEO Control Plane

by ai.thinkneo
OverviewDiscussionsAdmin

thinkneo_end_trace

End an active agent trace and get the session summary. Returns total cost, duration, tool/model call counts, and event count. Triggers post-session anomaly detection (cost spikes, error rate). Requires authentication.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoFinal session status: 'success', 'failure', or 'timeout'success
session_idYesSession ID from thinkneo_start_trace

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / session_id
      Added value: +{
+  "description": "Session ID from thinkneo_start_trace",
+  "title": "Session Id",
+  "type": "string"
+}
    • addedInput schema / properties / status
      Added value: +{
+  "default": "success",
+  "description": "Final session status: 'success', 'failure', or 'timeout'",
+  "title": "Status",
+  "type": "string"
+}
    • removedInput schema / properties / trace_id
      Removed value: -{
-  "description": "Trace ID to end",
-  "title": "Trace Id",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "trace_id"
-]New value: +[
+  "session_id"
+]
  2. Changed4 schema fields changed
    • removedInput schema / properties / session_id
      Removed value: -{
-  "description": "Session ID from thinkneo_start_trace",
-  "title": "Session Id",
-  "type": "string"
-}
    • removedInput schema / properties / status
      Removed value: -{
-  "default": "success",
-  "description": "Final session status: 'success', 'failure', or 'timeout'",
-  "title": "Status",
-  "type": "string"
-}
    • addedInput schema / properties / trace_id
      Added value: +{
+  "description": "Trace ID to end",
+  "title": "Trace Id",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "session_id"
-]New value: +[
+  "trace_id"
+]
  3. Added

TDQS

A4.2/5.0
Behavior4/5

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

The description discloses behavioral traits beyond the annotations: it triggers post-session anomaly detection and requires authentication. The annotations are sparse (readOnlyHint=false, etc.), so this additional context is valuable. It does not contradict the annotations.

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 and well-structured: the first sentence states the primary action, the second lists return contents, and the third mentions side effects and authentication. Every sentence adds value with no 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?

For a tool with an output schema and clear annotations, the description covers the essential aspects: purpose, return values, side effects, and authentication. It could mention idempotency or behavior when no trace is active, but these are not critical given the output schema's detail.

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?

The input schema already provides full descriptions for both parameters (session_id and status), so the description adds minimal extra meaning. The schema coverage is 100%, so the baseline of 3 is appropriate.

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 function with a specific verb ('End'), the resource ('active agent trace'), and the outcome ('get the session summary'). It also lists what the summary contains, distinguishing it from sibling tools like thinkneo_start_trace and thinkneo_get_trace.

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 implies when to use the tool: when you want to end an active trace and retrieve its summary. It does not explicitly mention alternatives or exclusions, but the context (ending a trace) is clear and distinct from starting or viewing a trace.

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

All ThinkNEO Control Plane toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources