Skip to main content
Glama
Sign In

Fastero

by com.fastero
OverviewDiscussionsAdmin

Read page data

fastero_get_page_data
Read-only

Return the current rows of one widget a hosted page declares, as { rows, lastUpdated, truncated }. The live page card that fastero_show_page draws calls it for each widget, and it is marked app-only so the numbers stay out of the conversation; to read a page's HTML and widget names, fastero_get_page, and to show a page, fastero_show_page. Rows come from a recent cached result, else a fresh run of the widget's saved query, else the last stored copy, a spreadsheet widget's from its spreadsheet, and a notebook-cell widget's from its notebook's last run (a cell that cannot give rows, such as one showing no table, is refused with what to change); lastUpdated says when they were taken, and a long result is cut, with truncated true. name is the widget's name as the page declares it: a name the page did not declare is refused, as is one whose widget was deleted, and a page deleted or not in this project answers "Page not found". Any project member, viewers included, can read it.

Input Schema

NameRequiredDescriptionDefault
nameYesThe widget's name as the page declares it (widgets in fastero_get_page).
pageIdYesA hosted page’s id, from fastero_list_pages.
projectIdYesThe project’s id, from fastero_list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / name / description
      Added value: +"The widget's name as the page declares it (widgets in fastero_get_page)."
    • addedInput schema / properties / pageId / description
      Added value: +"A hosted page’s id, from fastero_list_pages."
    • addedInput schema / properties / projectId / description
      Added value: +"The project’s id, from fastero_list_projects."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well past readOnlyHint/destructiveHint: it discloses the data-provenance cascade (recent cache, then a fresh run of the saved query, then last stored copy, with spreadsheet and notebook-cell special cases), truncation with truncated=true, refusal behavior for undeclared or deleted widgets, 'Page not found' for deleted or cross-project pages, and that any project member including viewers can read it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the return shape, which is good, but the rest is one dense run-on paragraph blending provenance, errors, permissions and truncation into semicolon-chained clauses. Every fact earns its place, yet the structure makes it harder to scan than it needs to be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations beyond read-only hints, the description still covers return fields, freshness semantics, truncation, error responses and authorization. An agent has everything needed to call it and interpret the result.

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%, so the baseline is 3; the description adds real meaning for `name` by requiring it to be a name the page actually declares (cross-referencing fastero_get_page) and by describing the refusal that follows an undeclared or deleted widget name. projectId and pageId are left entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (return the current rows of one widget declared by a hosted page) and immediately gives the return shape { rows, lastUpdated, truncated }. It explicitly distinguishes itself from fastero_get_page (HTML and widget names) and fastero_show_page (display).

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?

Names the two closest siblings and what each is for, so the agent can route correctly, and discloses that the tool is marked app-only so the data stays out of the conversation. It stops short of stating an explicit 'use this instead of X when Y' rule, but the alternatives are clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Fastero toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources