Skip to main content
Glama

Describe the hub

describe_hub
Read-onlyIdempotent

Identify an Armature hub before querying: returns its name, shared or workspace type, API revisions, caller identity, capabilities and settings, and how this server reads it.

Instructions

What this Armature hub is: the instance's name, whether it is a shared hub or a person's workspace hub, the API revisions it serves, how it identifies callers, and its capabilities with their settings (coverage thresholds, export profiles); and how this server reads it. Ask this first in a conversation; the other tools' answers name the commit they read.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "describe_hub"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: it explains that the response includes settings such as coverage thresholds and export profiles, and that the result anchors how the server reads the hub, which reframes every other tool's output. No auth or rate-limit notes, so not a 5.

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

Conciseness3/5

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

The opening enumeration is a single long run-on clause with nested parentheticals that is harder to scan than it needs to be. The most actionable sentence, "Ask this first in a conversation," sits at the end rather than being front-loaded. Nothing is redundant, but the structure buries the guidance.

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?

With no output schema, the description must carry the return contract, and it does so by listing the fields the agent will receive. Combined with the sequencing advice, an agent knows both what comes back and when to call it. It stops short of describing the response shape or format, which is the only remaining gap.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly implies a no-argument call by framing the tool as a first-step orientation read.

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

Purpose4/5

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

The description uses a specific verb (describe) on a specific resource (the Armature hub) and enumerates the content: instance name, shared vs. personal hub, API revisions, caller identification, and capabilities with settings. That is far more than a restatement of the title. It does not explicitly contrast itself with the sibling describe_schema, so it falls short of a 5.

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?

"Ask this first in a conversation" gives an unambiguous ordering rule, and the clause about other tools' answers naming the commit explains why. There is no explicit when-not or named alternative, but the sequencing instruction is actionable and specific.

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