Skip to main content
Glama
verivus-oss

llm-cli-gateway

by verivus-oss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

explain_effective_config

Read-only

Determine which Personal Agent Config release is effective for a given workspace and explain its context provenance, keeping local paths and instruction text private.

Instructions

Explain the selected Personal Agent Config release and context provenance without returning local paths or instruction text.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceNoRegistered workspace alias for remote HTTP/OAuth provider calls. Do not use this field, workspace_list, or workspace_register_existing_repo as a fallback for stdio/local provider path access; pass workingDir/addDir/includeDirs directly instead.
workingDirNoAbsolute working directory whose Personal Agent Config Kit scope should be inspected. Relative paths are rejected so scope never depends on the gateway process cwd.
requestInstructionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true. Description adds value by specifying that local paths and instruction text are not returned, but does not elaborate further on behavior like whether it makes remote calls.

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?

Single sentence that is concise and front-loaded. It is efficient but could add more detail without being verbose.

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

Completeness3/5

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

Given no output schema, description does not specify what the returned 'explanation' looks like. It clarifies what is not returned but lacks details on the format or scope of the explanation. The three-parameter tool with one undocumented parameter adds to the gap.

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 67%. Description adds meaning to workspace (usage warnings) and workingDir (absolute path), but requestInstructions has no description in schema or description text. The description partially compensates for the coverage gap.

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?

Description clearly states the tool explains Personal Agent Config release and provenance, with a restriction on output. However, it does not explicitly differentiate from sibling tools like config_status or config_recover_kit_attempt.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives. A note in the workspace parameter about not using it for local path access is a parameter constraint, not usage context.

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