Skip to main content
Glama

Profile and onboarding

spur_get_workspace
Read-onlyIdempotent

Read your profile/business identity, onboarding checklist, available outreach strategies, or monday.com connection and list-sync status. Never returns another user's account.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "section": "<section>"
    },
    "name": "spur_get_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
refreshNo
sectionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds one genuine behavioral guarantee beyond that — "Never returns another user's account" — which tells the agent the scope is self-only. It says nothing about caching or what the boolean refresh actually changes, which is the one behavioral trait the annotations do not cover.

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?

Two short sentences with zero filler; the enumerated sections are front-loaded and the scope guarantee follows as a compact qualifier. Nothing repeats the tool name or title, and no sentence is wasted.

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?

For a simple read-only tool with rich annotations this is close to adequate, but it returns four structurally different payloads and there is no output schema, so the agent gets no hint about return shape for any section. The undocumented refresh flag and the absence of any guidance on which section to query when leave a visible 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 description coverage is 0%, so the description must carry parameter meaning. It does partially: the four section semantics are spelled out (profile ≈ business identity, onboarding ≈ checklist, strategies ≈ available outreach strategies, monday ≈ connection and list-sync status), which is real added value over the bare enum. However, the refresh parameter is never mentioned anywhere, so one of the two parameters is undocumented in both schema and description.

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 uses a specific verb ("Read") and enumerates the exact resources available: profile/business identity, onboarding checklist, outreach strategies, and monday.com connection/list-sync status. An agent can immediately tell this is the read-side counterpart to spur_update_workspace, though the sibling is never named explicitly.

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?

By listing the four things it reads, the description implies that callers pick the relevant section, but it never states when to choose this over spur_update_workspace or when each section is appropriate. There are no exclusions or preconditions (e.g. 'requires an existing monday.com connection').

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