Skip to main content
Glama

SourceGeek

Read sheet or document

read_artifact
Read-only

Read the latest content of an existing artifact. Returns the artifact metadata and its raw content (CSV for sheets, markdown for text). Use this to access artifact data for further processing — e.g. exporting to Google Sheets, filtering rows, or feeding into another tool.

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

Input Schema

NameRequiredDescriptionDefault
idNoThe artifact id to read. If omitted, reads the latest artifact in the thread.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 safety is covered. The description adds real value beyond that by disclosing the return payload: artifact metadata plus raw content, with format depending on artifact type (CSV for sheets, markdown for text). It does not cover failure behavior for a missing or inaccessible id.

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?

Three short sentences: what it does, what it returns, and when to use it. Nothing repeats the annotations or the schema, and the essential action is front-loaded.

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?

There is no output schema, so the description's disclosure of return shape and format is exactly the missing piece and it delivers it. For a single-optional-parameter read tool this is nearly complete, though error and empty-artifact behavior are unstated.

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% and the id property already documents the default-to-latest-thread behavior, so the description cannot add much. It only implies the target must be "an existing artifact", which is consistent with, but not richer than, the schema.

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 the latest content of an existing artifact") and scopes it to the latest version. An agent can distinguish it from write-side siblings like create_sheet, though no sibling is named explicitly.

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

Usage Guidelines4/5

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

The third sentence gives clear when-to-use context with concrete downstream examples (exporting to Google Sheets, filtering rows, feeding another tool). There are no exclusions or named alternatives for cases where another read tool would be preferable, which keeps it out of 5 territory.

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