Skip to main content
Glama

Vee3

by io.github.Vee3io

meta-tools.describe

Describe a single Vee3 capability.

Pass the MCP tool name (for example website-screenshots.capture) or capability id (for example website-screenshot). Use this after meta-tools.list_group_tools when you need parameter names, defaults, response fields, examples, and token cost before calling a tool

Cost = 0 tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tool_nameYesMCP tool name (for example `x-twitter.create_post`) or capability id (for example `create-x-post`).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolNoFull capability detail including fields, examples, and bindings.
capability_idNoDescribed capability id.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • changedOutput schema / $defs / DescribeToolResponseToolRequestFieldsItem / properties / default / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "integer"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedOutput schema / $defs / DescribeToolResponseToolRequestFieldsItem / properties / default / description
      Previous value: -"Default value when omitted, or null when none."New value: +"Default value when omitted (string, integer, or boolean), or null when none."
  2. Changed3 schema fields changed
    • removedInput schema / properties / capability_id
      Removed value: -{
-  "description": "MCP tool name (for example `x-twitter.create_post`) or capability id (for example `create-x-post`).",
-  "maxLength": 128,
-  "title": "Capability Id",
-  "type": "string"
-}
    • addedInput schema / properties / tool_name
      Added value: +{
+  "description": "MCP tool name (for example `x-twitter.create_post`) or capability id (for example `create-x-post`).",
+  "maxLength": 128,
+  "title": "Tool Name",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "capability_id"
-]New value: +[
+  "tool_name"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / capability_id / description
      Previous value: -"Capability id (for example create-x-post) or MCP tool name (for example x-twitter.create_post)."New value: +"MCP tool name (for example `x-twitter.create_post`) or capability id (for example `create-x-post`)."
  4. Changed8 schema fields changed
    • changedInput schema / properties / capability_id / description
      Previous value: -"Capability id to describe (for example website-screenshot)."New value: +"Capability id (for example create-x-post) or MCP tool name (for example x-twitter.create_post)."
    • removedOutput schema / $defs / DescribeToolResponseTool / properties / capability_id
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Capability id (for example website-screenshot).",
-  "title": "Capability Id"
-}
    • removedOutput schema / $defs / DescribeToolResponseTool / properties / display_name
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Human-readable capability name.",
-  "title": "Display Name"
-}
    • removedOutput schema / $defs / DescribeToolResponseTool / properties / group_display_name
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Human-readable group name.",
-  "title": "Group Display Name"
-}
    • removedOutput schema / $defs / DescribeToolResponseTool / properties / rest_method
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "HTTP method for the REST endpoint.",
-  "title": "Rest Method"
-}
    • removedOutput schema / $defs / DescribeToolResponseTool / properties / rest_path
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "REST path for the capability.",
-  "title": "Rest Path"
-}
    • removedOutput schema / $defs / DescribeToolResponseTool / properties / status
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Capability status (live, soon, or deprecated).",
-  "title": "Status"
-}
    • removedOutput schema / $defs / DescribeToolResponseTool / properties / token_cost
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "API tokens charged for one successful call.",
-  "title": "Token Cost"
-}
  5. First observed

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses that the operation costs 0 tokens and that it returns parameter names, defaults, response fields, examples, and token cost. It is clearly a read-only informational tool, though it does not describe error behavior or what happens with invalid names.

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 short and well-structured, leading with the purpose, then providing examples of accepted inputs, usage timing, and cost. Every sentence adds useful information with no filler, making it highly efficient.

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 tool's simplicity, an output schema exists, and the description covers when to use it and what information it returns, the context is mostly complete. It assumes prior knowledge of Vee3 capabilities, but this is reasonable given the sibling tool set and the tool's meta-purpose.

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 description coverage is 100%, and the schema description for 'tool_name' already explains it accepts an MCP tool name or capability id. The description repeats this but adds no additional semantic meaning beyond giving more examples, so it meets the baseline without elevating it.

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 states 'Describe a single Vee3 capability' with a specific verb and resource, and further clarifies it takes a tool name or capability id. This clearly distinguishes it from sibling tools like meta-tools.list_group_tools by focusing on a single capability and the detailed information it returns.

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?

Explicitly states to use this tool 'after meta-tools.list_group_tools when you need parameter names, defaults, response fields, examples, and token cost before calling a tool.' This gives a clear context and trigger, though it does not explicitly mention when not to use it or name alternatives beyond the sequential reference.

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

All Vee3 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool has a distinct purpose, further clarified by group prefixes and clear descriptions. Within each group, tools perform different operations (e.g., domains.lookup vs. domains.whois vs. domains.rdap) with no ambiguity.

Naming Consistency5/5

All tools follow a consistent group.tool_name pattern using snake_case. The naming is predictable and uniformly applied across all groups.

Tool Count4/5

78 tools is high, but the server aggregates multiple distinct API domains (11 groups). Each group has a reasonable number of tools, typically under 10, with TikTok having 17. The count reflects breadth, not bloat.

Completeness5/5

Each domain's tool set covers the primary expected operations (e.g., search, details, reviews, metrics, user info). There are no obvious gaps for read-only analytical use; features like posting are likely out of scope.

Resources