Skip to main content
Glama

SourceGeek

Get workspace context entry

get_workspace_context
Read-only

Read one workspace context entry (full markdown content) by its key, e.g. tone-of-voice, company-profile, company-background, company-jobs.

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": {
      "key": "<key>"
    },
    "name": "get_workspace_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesThe entry key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 needs no restating. The description does add one useful behavioral fact beyond them — that the full markdown content is returned, not a summary — but says nothing about missing-key behavior or content size.

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?

A single sentence with the return payload and the lookup key front-loaded, followed by illustrative values. No filler, no redundancy with the schema or title.

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 one-parameter read tool with no output schema, the description covers the essential unknowns: what is fetched and in what form (full markdown). The remaining gap is error/empty behavior for an unknown key, which is minor but not covered anywhere else.

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 the schema only says 'The entry key.', so the baseline would be 3. The description earns above baseline by supplying concrete example keys (tone-of-voice, company-profile, company-background, company-jobs), which materially help an agent construct a valid value.

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?

States a specific verb and resource ('Read one workspace context entry') plus the selection key, which implicitly separates it from the list/upsert/delete siblings. It does not name an alternative tool outright, so differentiation is inferred from the singular 'one ... by its key' framing rather than stated.

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?

Usage is implied: call this when you already know the entry key. The description gives no explicit when-to-use guidance, no pointer to list_workspace_context for discovering keys, and no statement about what happens if the key does not exist.

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