Skip to main content
Glama
Pedra MCP Server

Pedra MCP Server

Official
by pedra-ai

Check multi-angle staging

pedra_get_furnish_same_room
Read-only

Check the status of a same-room furnishing job by jobId, returning processing, ready, partial, or failed plus per-photo output statuses and URLs when ready, without spending credits.

Instructions

Check a job started with pedra_furnish_same_room. Returns status "processing", "ready", "partial" (some photos failed and weren't charged) or "failed", plus one output per photo in the order sent, each with its own status and, once ready, its url. Never spends credits.

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": {
      "jobId": "<jobId>"
    },
    "name": "pedra_get_furnish_same_room"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesId returned by pedra_furnish_same_room.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.8.0

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations by enumerating all four job states, explaining that "partial" means some photos failed and were not charged, describing one output per photo in submission order, and stating "Never spends credits" — a business-relevant guarantee the readOnlyHint does not convey.

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?

Two tightly packed sentences that front-load the action, then the return contract. No filler, and the status enumeration is scoped to exactly what the caller must branch on.

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?

Because there is no output schema, the description carries the full return-value burden and does so thoroughly with state names and per-photo results. Minor gaps remain around polling cadence and result retention, which matter for an asynchronous status endpoint.

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?

The single jobId parameter is already fully documented in the schema (100% coverage) as the id returned by pedra_furnish_same_room, and the description adds no format, expiry, or reuse detail beyond that. Baseline 3 is appropriate when the schema does the work.

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?

Specific verb+resource: checks the status of a job started with pedra_furnish_same_room, and it names that sibling explicitly. An agent can immediately tell this is a poll/status tool rather than an action tool.

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?

Clear context: this is the follow-up to pedra_furnish_same_room, so when-to-use is evident from the phrasing. It lacks any guidance on polling cadence, whether to poll repeatedly until "ready", or long results persist.

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