Skip to main content
Glama
Sign In
Agent Guild

Agent Guild

by oddessentials
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Agent Guild status

guild_status
Read-only

Check whether Agent Guild is running on this computer and report its version plus the number of active terminal sessions, so you can confirm the service is available before steering sessions.

Instructions

Whether Agent Guild is running on this computer, its version, and how many sessions it has. To customize a Yard, the characters and companions of a Yard or Agent Guild: World, or to install Grove Companion on the desktop, follow https://agentguild.oddessentials.ai/agents/.

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": "guild_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value by enumerating the three pieces of information returned (running state, version, session count), which matters because no output schema exists to document the response shape.

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

Conciseness4/5

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

The status answer is front-loaded in the first sentence, which is exactly the right ordering. The second sentence is somewhat tangential — an external documentation pointer for tasks this tool doesn't perform — but it plausibly prevents misuse, so it mostly earns its place.

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 zero-parameter read-only status check with no output schema, the description covers what is checked and what comes back. The only thing an agent might still want is whether to call this before session operations, which is a minor omission for a tool this simple.

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 beyond what the empty schema already conveys. Baseline of 4 applies; no parameter-level gaps exist.

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 names the resource (Agent Guild) and states exactly what the tool reports: running state, version, and session count. That is more specific than a bare 'status' label and distinguishes it from session-oriented siblings like list_sessions or start_session, though it never explicitly contrasts itself with them.

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?

Usage is only implied — an agent can infer this is a pre-flight/health check before starting sessions, but the description never says 'call this before start_session' or similar. The second sentence does usefully redirect away from this tool for customization and installation tasks, but it routes to an external URL rather than to any sibling tool.

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