Goodeye

grant_skill

Grant skill access to a user or team by UUID, email, or handle.

By default the grantee sees the skill version current at share time and any later versions, but not older ones. Set include_history to true to give the grantee the full version history.

Input Schema

TableJSON Schema

Name	Required	Description
`role`	Yes	Access level to grant: 'view', 'edit', or 'admin'.
`skill_id`	Yes	The skill to act on, identified by its UUID, slug, or name.
`include_history`	No	When true, the grantee sees the full version history; when false (default), only the version current at share time and later.
`grantee_email_or_at_team_handle`	Yes	The grantee: a user's email, or a team's @handle.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedJul 18, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations are minimal (non-read-only, non-destructive). The description adds valuable context about version history handling, which is not covered by annotations. No contradictions.

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?

Two sentences, no wasted words. The key information is front-loaded and easy to parse.

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?

Given the presence of an output schema (not shown but declared), all parameters are well-documented in schema, and the description covers the behavioral nuance of version history. Complete for this tool.

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?

Schema coverage is 100%, so baseline is 3. The description adds meaning by explaining the default and effect of include_history, and the flexible identifier formats for the grantee.

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 clearly states the tool's purpose: granting skill access to a user or team by identifier. It distinguishes from siblings like revoke_skill_grant and list_skill_grants by focusing on granting access.

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?

Provides clear context on the include_history parameter and default behavior. Does not explicitly state when not to use this tool or compare with siblings, but the use case is straightforward.

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

All Goodeye tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.