Skip to main content
Glama

Get Workspace Summary Tool

get-workspace-summary
Read-only

Returns a limited, read-only summary of the authenticated FieldRobin workspace. Use to inspect the workspace summary in the connected business. Returns business, counts, scope.

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": "get-workspace-summary"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
scopeYesAuthorization scope of this result; data remains restricted to the connected business.
countsYesCounts data returned by the authorized safe projection.
businessYesBusiness data returned by the authorized safe projection.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "business": {
      +      "description": "Business data returned by the authorized safe projection.",
      +      "type": "object"
      +    },
      +    "counts": {
      +      "description": "Counts data returned by the authorized safe projection.",
      +      "type": "object"
      +    },
      +    "scope": {
      +      "description": "Authorization scope of this result; data remains restricted to the connected business.",
      +      "enum": [
      +        "active_business"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "business",
      +    "counts",
      +    "scope"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

B3/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 safety is covered. The description adds the notion of an "authenticated" workspace scope and a deliberately "limited" result, which hints at truncation, but it never explains what is capped or how the payload is bounded.

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?

Three short sentences, but the middle one duplicates the first, and the closing field list ("business, counts, scope") is too terse to be informative. Front-loaded purpose is fine; the rest does not fully earn its space.

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?

A zero-argument, read-only tool with annotations and an output schema needs little explanation, and the description covers the essentials. Still missing is what "limited" means in practice and when an agent should call this rather than one of the report or entity-lookup siblings.

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 no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The mention of business, counts, and scope concerns the response, not inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Returns a limited, read-only summary of the authenticated FieldRobin workspace" names a resource and an output shape, but it largely restates the tool name and title. It does not differentiate this workspace-level summary from report-style siblings such as reports-overview or reports-by-location.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use to inspect the workspace summary in the connected business" is a restatement of purpose rather than guidance; there is no stated condition, prerequisite, or alternative tool to prefer in any situation.

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