Skip to main content
Glama

This workspace

workspace
Read-only

The product this key belongs to: name, URL, the account's balance in dollars (the free credit while it lasts, and what was paid), the access summary, tracking state, and the links to the results app and proof page, plus whether the repo you are in is this site's code. Free. Call this first, with repo.

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

Input Schema

NameRequiredDescriptionDefault
growNotrue when this is the start of grow (the daily routine): Shipfound starts judging today's moves now, so they are ready when you call today.
repoNoThe founder's project you are working in: the output of `git remote get-url origin` there, or the folder name when it has no remote. Credentials in the URL are dropped, never stored.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / grow
      Added value: +{
      +  "description": "true when this is the start of grow (the daily routine): Shipfound starts judging today's moves now, so they are ready when you call today.",
      +  "type": "boolean"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / repo
      Added value: +{
      +  "description": "The founder's project you are working in: the output of `git remote get-url origin` there, or the folder name when it has no remote. Credentials in the URL are dropped, never stored.",
      +  "maxLength": 300,
      +  "type": "string"
      +}
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds two traits beyond that: the call is 'Free' (no billing impact) and it should be invoked first — both genuinely useful. It says nothing about failure modes, what happens with an invalid key, or rate/refresh behaviour, so the added context is modest.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single run-on sentence built around a colon list of return fields, with the action-ordering advice ('Call this first, with `repo`') trailing at the end rather than front-loaded. Every element earns its place as return-field information, but the structure makes an agent parse a dense clause chain to find the instruction.

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?

There is no output schema, and the description compensates by enumerating the returned fields, which is exactly what an agent needs to decide whether to call it. Both parameters are documented at 100% coverage and the call-first ordering is stated. Minor gaps remain around error behaviour and what 'tracking state' or 'access summary' actually contain.

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%, and both `grow` and `repo` already carry detailed descriptions, including the credential-stripping note. The description only reinforces that `repo` should be supplied even though it is optional; it adds little semantic detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 names the resource ('the product this key belongs to') and enumerates the exact contents: name, URL, dollar balance split between free credit and paid, access summary, tracking state, links to the results app and proof page, and whether the local repo is this site's code. That is concrete enough for an agent to know what it gets back. It stops short of naming a sibling it is not (e.g. `access`), so it is clear but not fully differentiated.

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?

'Free. Call this first, with `repo`.' gives an explicit invocation order and a recommended argument, which is real routing guidance rather than an implied suggestion. It does not state when to skip this tool or which sibling to prefer after it, so no explicit exclusion is present.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources