Skip to main content
Glama

SourceGeek

Read a task and its result

read_task
Read-only

Read one SourceGeek task by key (e.g. SBE-12): its title, status, description, the result SourceGeek posted when it finished, the latest comments, the sheets and documents its chat made (id, kind, title, URL), and links to the task and its chat in SourceGeek.

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": {
      "task": "<task>"
    },
    "name": "read_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesThe task's key, e.g. SBE-12.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/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 is covered. The description adds real value beyond that by disclosing the shape and richness of the payload in a single call — including that it surfaces the result SourceGeek posted on completion, comments, and generated sheets/documents. It says nothing about behavior when the key is unknown, permissions, or freshness, which keeps it below a 5.

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?

It is a single front-loaded sentence that states the operation first and then the returned contents, with no filler or marketing language. The return-value list is long, but every item is load-bearing because there is no output schema. Slightly dense, yet efficient.

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 correctly takes on the job of describing return contents in detail, and the single required parameter is fully documented by the schema. Missing are edge behaviors an agent might want — what happens for an unknown key, whether comments are truncated or paginated, and whether artifacts are always present. These are gaps but not blockers for correct invocation.

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 only one parameter and schema coverage is 100%, with the schema itself supplying 'The task's key, e.g. SBE-12.' The description repeats the same key format ('by key (e.g. SBE-12)') without adding syntax, case sensitivity, or lookup rules. With the schema doing the heavy lifting, the baseline 3 applies.

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 opens with a specific verb and resource ('Read one SourceGeek task by key') and enumerates exactly what comes back: title, status, description, posted result, latest comments, chat artifacts with id/kind/title/URL, and deep links. That is far more concrete than a restated title. It stops short of naming a sibling such as read_artifact or read_shortlist_feedback, so an agent must infer the boundary itself.

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 only implied: the agent can infer it should call this when it holds a task key like SBE-12 and wants the task plus its output. There is no explicit when-to-use statement, no when-not-to-use, and no pointer to an alternative for listing or searching tasks. Adequate for a simple read-by-key tool, but the guidance is left to inference.

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