Skip to main content
Glama
yutori-ai

Yutori MCP

Official
by yutori-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_scout_detail

Read-only

Retrieve full details for a specific scout by providing its scout ID, enabling targeted monitoring and research.

Instructions

Get detailed information about a specific scout.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scout_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / description
      Removed value: -"Input for operations on a specific scout."
    • removedInput schema / properties / scout_id / description
      Removed value: -"The scout's unique identifier (UUID)"
    • changedInput schema / title
      Previous value: -"ScoutIdInput"New value: +"get_scout_detailArguments"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_scout_detailOutput",
+  "type": "object"
+}
  2. Changed1 schema field changedv0.3.0
    • addedInput schema / additionalProperties
      Added value: +false
  3. First observedv0.2.9

TDQS

A3.6/5.0
Behavior3/5

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

Annotations provide readOnlyHint=true, so description does not add behavioral context beyond that. No mention of side effects, permissions, or rate limits. Adequate but not enhanced.

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?

Single sentence with no wasted words. Front-loaded with verb and noun. Perfectly concise.

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?

Tool is simple with 1 param and output schema present, so description is minimally adequate. However, additional context about the scope of 'detailed information' could improve completeness.

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

Parameters2/5

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

Schema has 0% description coverage and parameter is only named 'scout_id' with type string. Description does not clarify format (e.g., UUID, integer) or provide any additional meaning.

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?

Description clearly states verb 'Get' and resource 'scout' with scope 'detailed information' and specificity. It distinguishes from siblings like list_scouts (list all) and mutation tools (create, delete, edit).

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

Usage Guidelines3/5

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

No explicit when or when-not guidance, but usage is implied: use when you need details of a specific scout. No mention of alternatives like get_scout_updates.

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