gryzzly-mcp

get_group

Read-only

Retrieve one Gryzzly group by ID to view its name, groupset, and manager.

Instructions

Read one group by identifier: its name, its groupset, its manager.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	The object's identifier.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	The group's identifier.
`name`	No	The group's name.
`created_at`	No	When the group was created.
`manager_id`	No	The group's manager.
`updated_at`	No	When the group was last updated.
`groupset_id`	No	The groupset the group belongs to.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 20, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the identity of the returned fields, but does not mention permissions, rate limits, or failure behavior for a missing id. With annotations carrying the main burden, this is an adequate but modest contribution.

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?

A single economical sentence with the core action front-loaded and the returned fields listed after the colon. No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter lookup with an output schema present, the description is complete: it identifies the operation, the key, and the returned fields. Nothing essential for correct invocation is missing.

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 coverage is 100%, so the single id parameter is already fully documented in the schema. The description only restates that lookup is 'by identifier', adding no syntax, format, or example beyond the structured data. Baseline 3 is appropriate.

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 states a specific verb and resource ('Read one group by identifier') and names the fields returned (name, groupset, manager). It implicitly distinguishes itself from list_groups by saying 'one group', but never explicitly names a sibling as the alternative.

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 implied: fetch a single group when you have its identifier. There is no explicit when-to-use, when-not-to-use, or pointer to a sibling like get_groupset or list_groups, so the agent must infer the routing.

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