Skip to main content
Glama
Claude Free Code MCP

Claude Free Code MCP

by ImIpscanning

workspace_info

Read-only

Displays the project root, project type, execution limits, and capabilities so you can verify workspace configuration before running commands or tests.

Instructions

Show project root, project type, configured execution limits and capabilities.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. The description earns credit beyond that by enumerating exactly what the call reports (root, type, execution limits, capabilities), which matters because there is no output schema. It stops short of describing format or whether values can be absent.

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?

One short sentence listing the returned items in a natural reading order, with zero filler. Every word contributes to identifying the tool's output.

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 parameterless, non-destructive introspection tool without an output schema, naming the reported fields is close to sufficient. A brief note on how the values are formatted or whether they can be empty would close the remaining gap.

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 the baseline is 4. Nothing in the description misleads about inputs, and no additional parameter meaning is needed.

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?

Uses a specific verb ('Show') with an enumerated set of resources: project root, project type, execution limits and capabilities. An agent can tell this is a project-introspection tool, though it does not explicitly contrast itself with lookalikes such as project_tree or project_notes_read.

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?

No explicit when-to-use or when-not-to-use statement and no named alternatives. The read-only discovery intent is implied by the resource list, but an agent must infer that this is the first call to make when orienting in a workspace.

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