Skip to main content
Glama

SourceGeek

List my sheets and documents

list_artifacts
Read-only

List the user's own recent SourceGeek sheets and documents in this workspace (created in SourceGeek or through this connector), newest first. Returns id, kind, title, last update and URL for each.

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

Input Schema

NameRequiredDescriptionDefault
kindNoOnly sheets (candidate lists, trackers) or only text documents (shortlists, dossiers).
limitNoHow many to return (1-50, default 20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the description's added value is the ordering guarantee ("newest first") and the returned field set (id, kind, title, last update, URL) in the absence of an output schema. It says nothing about pagination, whether results are capped by workspace membership, or what an empty result looks like — useful but not rich.

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?

Two sentences, front-loaded with the verb and scope, and the return payload enumerated last. No filler or repetition of the title verbatim beyond what is needed. Efficient for the amount of information conveyed.

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 zero-required-parameter read tool with full schema coverage and annotations, this is close to sufficient: scope, ordering, and return fields are all stated. Minor gaps remain around pagination and whether results are limited by workspace permissions, but nothing an agent needs to invoke it correctly is missing.

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 100%, with both parameters documented including the enum values and the 1-50 range with default. The description adds nothing about parameters beyond the schema; "recent" gestures at ordering/default limit but gives no format guidance. 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?

Specific verb and resource ("List the user's own recent SourceGeek sheets and documents") with scoping qualifiers: own, this workspace, created in SourceGeek or through this connector, newest first. An agent can tell it returns a personal artifact inventory. It stops short of naming a sibling it must not be confused with (e.g. list_workspace_context), so a 4 rather than a 5.

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?

The scope clauses imply when this is the right call (personal, SourceGeek-created artifacts in this workspace), but there is no explicit when-to-use vs when-not, and no pointer to alternatives such as list_workspace_context or the cbs_* table tools. Usage is inferable rather than stated.

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