Skip to main content
Glama

Shipfound

by co.shipfound.api
OverviewDiscussionsAdmin

This workspace

workspace
Read-only

The product this key belongs to: name, URL, plan, credits left, 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.

Input Schema

NameRequiredDescriptionDefault
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. 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"
+}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the bar is lower. The description adds real behavioral context beyond them: it declares the call is Free and should be the first call, and the schema notes credentials in the URL are dropped and never stored. It doesn't describe response format or pagination, but neither is expected for a small context read.

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?

A single tight sentence enumerating the payload, followed by a short actionable directive ("Free. Call this first, with `repo`"). The enumeration is dense but every listed item is information the agent would otherwise lack, so little is wasted.

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?

With no output schema, the description carries the burden of describing what comes back, and it does so thoroughly by listing the returned fields. It is complete enough to call correctly; only the response's structure/nesting is left unspecified, which is minor for a flat context call.

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% and there is only one optional parameter, so baseline is 3. The description adds a bit more by instructing the agent to supply `repo` on the call, clarifying intended usage of a parameter the schema marks optional.

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 enumerates exactly what the tool surfaces about the current workspace: product name, URL, plan, credits, access summary, tracking state, results-app/proof-page links, and whether the current repo is this site's code. That is a clear resource-and-contents statement, though it never states a verb (read/describe) and doesn't explicitly contrast itself with similarly-named siblings like access or record_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?

"Free. Call this first, with `repo`" gives explicit ordering and cost guidance, which is strong when-to-use context. It does not name alternatives or when-not-to-use conditions, so it stops short of a 5.

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

All Shipfound toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources