Skip to main content
Glama

Archlooks.com - Interior design and architecture gallery

Get project metadata

get_project_card
Read-only

Public metadata card for one project: title, designer, location, type, preview image, canonical URL, license note. Same payload as GET /x402/card/{id}.json.

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": {
      "project_id": "<project_id>"
    },
    "name": "get_project_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesNumeric project id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, and the description adds real context beyond it: the payload is public-facing, its fields are enumerated, and it is declared byte-identical to GET /x402/card/{id}.json, which lets an agent reason about output shape from existing HTTP docs. Auth requirements and not-found behavior remain unstated.

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 sentences, front-loaded with the resource and followed by the payload contents plus an endpoint-equivalence anchor. No filler or restated title.

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 single-parameter read tool with readOnlyHint and no output schema, the field enumeration effectively substitutes for a return schema. Only failure modes (unknown/private project id) are left uncovered, a minor gap at this complexity.

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% — project_id is typed, patterned and described as a numeric id — so the schema does the work. The description adds no extra meaning about id format or lookup failures, so the 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?

States a specific verb/resource pair ('Public metadata card for one project') and enumerates exactly what the card contains: title, designer, location, type, preview image, canonical URL, license note. The word 'public' and the card-vs-full-record framing implicitly separate it from access_project, though it never names the sibling.

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?

Usage is only implied: fetch a lightweight public card for a known project id. There is no explicit 'use this instead of access_project when...' routing or exclusion, so an agent must infer the boundary itself.

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