Manage version control for FlowState shared memory by initializing repositories, checking status, syncing changes, cloning, and viewing history across AI apps and machines.
Git operations. Actions: init, status, sync, set_remote, clone, history
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| action | Yes | ||
| local_path | No | ||
| remote_url | No | ||
| commit_message | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and openWorldHint=true, but the description adds no behavioral context such as which actions mutate local state, which reach the network, or what sync/clone overwrite. It neither reinforces nor contradicts the safety profile, leaving the agent to infer risk per action.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded and compact with no filler, so it reads quickly. But it is thin rather than efficient for a six-action tool with five undocumented parameters, straying into under-specification.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a multiplexed, network-reaching, destructive-capable tool with five parameters at 0% coverage and no output schema, the description is inadequate. An agent cannot determine parameter applicability per action or the risk profile of individual actions from this text.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% and the description does not compensate: local_path, remote_url, commit_message, and limit are never explained, and it does not indicate which parameters apply to which action. It only restates the action enum, which the schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States the resource (Git operations) and enumerates six actions, so an agent knows it's a multiplexed Git tool. However, it does not differentiate from siblings (notably a separate 'history' sibling tool that overlaps with the 'history' action here), and the action list merely mirrors the schema enum.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use guidance, prerequisites, or alternatives are given. It offers no help deciding between actions (e.g. sync vs set_remote vs clone) or between this tool and the sibling 'history' tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.