Skip to main content
Glama
Sign In

mcp

by com.makehybrid
OverviewDiscussionsAdmin

MakeHybrid API: What this organization shows its people: surface (full for the whole dashboard, or app for the rooms app alone) and the caller's role.

complete_workspace_surface
Read-onlyIdempotent

What this organization shows its people: surface (full for the whole dashboard, or app for the rooms app alone) and the caller's role. -- MakeHybrid API plan, GET /workspace/surface, group workspace.

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

Input Schema

NameRequiredDescriptionDefault
queryNoOptional query-string parameters, e.g. {"limit":"20","cursor":"..."}. Values are coerced to strings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description does add real value by naming what comes back (the 'full' vs 'app' surface and the caller's role), partially compensating for the absent output schema. It says nothing about auth/scopes or pagination, which keeps it at 3.

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 short with no filler, but it is not front-loaded with an action: it opens with a payload description and tacks the endpoint metadata on after a '--' separator. The structure reflects generated spec text rather than agent-oriented framing.

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 low-complexity, zero-required-parameter read tool with full annotation coverage and no output schema, the description supplies the key missing piece: what the response contains (surface mode and caller role). What remains missing is any usage context or differentiation from siblings, but the core call-correctly information is present.

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?

There is a single optional 'query' object parameter with 100% schema description coverage, so the schema already carries the burden. The description adds no query syntax or filter examples beyond what the schema provides, which matches the baseline 3 for fully documented schemas.

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?

The text reads as a description of the response payload ('what this organization shows its people... and the caller's role') plus the endpoint 'GET /workspace/surface', so an agent must infer that this is a read of workspace surface configuration. There is no explicit verb and 'surface' is jargon, but the endpoint path and group name point to the resource. It is not a tautology, yet it does not clearly differentiate from complete_workspace_people.

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?

No guidance on when to call this versus the ~90 sibling tools, including the obvious neighbour complete_workspace_people. There are no prerequisites, no exclusions, and no stated scenario. The only usable hint is the endpoint path.

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

All mcp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources