Skip to main content
Glama

Read what a page collected

read_artifact_results
Read-onlyIdempotent

Every answer a page collected, by name: a survey's responses (one per person, with the questions), or the page's data documents with who wrote each. Only the page's owner, or an admin of the company that owns it, may read them. Use it to summarize a survey, count sign-ups, or say who has not answered. Answers carry names and email addresses: report what the user asked, not the raw rows.

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": {
      "artifact_id": "<artifact_id>"
    },
    "name": "read_artifact_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
artifact_idYesThe Artifact id (art_…): the last part of its link, as in bisque.cloud/documents/art_…, /pages/art_… or /artifacts/art_….

Output Schema

NameRequiredDescriptionDefault
kindYes
titleNo
documentsNo
questionsNo
responsesNo
truncatedYes
artifact_idYes
published_version_numberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description goes further with the authorization model ('only the page's owner, or an admin of the company that owns it') and a PII handling instruction ('answers carry names and email addresses: report what the user asked, not the raw rows') — behavioral context an agent cannot get from structured fields.

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?

Three tight sentences: what you get, who may read it, what to do with it. Front-loaded and free of filler. The final sentence mixes usage and privacy guidance, but every clause earns its place.

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 one fully documented parameter, an output schema, and rich annotations, the definition covers purpose, permissions and output interpretation. The only gap is scale behavior — nothing says what happens with large response sets (truncation, paging), which matters for a survey with many respondents.

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%: artifact_id is fully documented with a pattern and an explanation of how to derive it from links. The description adds nothing about the parameter, which is acceptable when the schema does all the work, so the baseline of 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 names the specific resource and its exact content: 'every answer a page collected, by name' — survey responses one per person with questions, or data documents with authors. That is far more precise than the title and separates it in substance from get_artifact or read_artifact_analytics, 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?

It gives three concrete triggering tasks — summarize a survey, count sign-ups, identify who has not answered — which is clear positive guidance. It stops short of stating when NOT to use it (e.g., for the page content itself use get_artifact, for metrics use read_artifact_analytics), so the boundary with siblings is left implicit.

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