Skip to main content
Glama

Homespun

by dev.homespun

Community Reviews

review
Destructive

Ratings and reviews of community templates, responses from a template's own publisher, and, for relay operators, moderation. Actions: create leaves a 1-to-5 star rating and an optional written body on a template the caller has installed, identifying it by template ("/") or by handle plus slug, and requires a verified email; each install yields exactly one review, and the aggregate carries across template versions. A body containing a link or a contact email is held automatically for a moderator before it appears. respond replies to a review of the caller's own template line (review_id plus response, or null to clear it), with one editable response per review. report flags a review for the relay's moderators (review_id plus reason) and is deduped per account. remove and unhold are limited to the relay's configured community reviewers: remove takes a review down and adjusts the rating aggregate, and unhold publishes a previously held review into the aggregate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNocreate only. Optional written review (up to 2000 chars).
slugNocreate only. Per-publisher slug (with `handle`).
starsNocreate only. Star rating, an integer 1 to 5.
actionYescreate: leaves a star rating (1..5) and optional body on a community template the caller has installed (identified by `template` "<handle>/<slug>" or by `handle`+`slug`); requires a verified email, and one review per install. A body containing a link or contact email is auto-held for a moderator before it shows. respond: replies to a review of one of the caller's own templates (review_id + response; null clears it). report: flags a review for the relay's moderators (review_id + reason; one report per account). remove / unhold are relay-operator-only moderation actions on a review_id: remove takes a review down (adjusting the aggregate), unhold publishes a previously auto-held review.
handleNocreate only. Publisher handle (with `slug`), an alternative to `template`.
reasonNoreport only. Why you are reporting this review (up to 500 chars).
responseNorespond only. The publisher's public response (up to 2000 chars); null clears it.
templateNocreate only. The namespaced template id <handle>/<slug> to review.
review_idNoRequired for respond/report/remove/unhold. The review's id.

TDQS

A4.5/5.0
Behavior5/5

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

The description goes well beyond annotations, disclosing important behaviors such as auto-holding bodies containing links/contact emails, aggregate carry across template versions, one-review-per-install limit, deduplication of reports, and how remove adjusts the aggregate. These details are not present in annotations and meaningfully inform the agent about side effects and moderation flows.

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?

The description is a single dense paragraph that front-loads the overall purpose before breaking down each action. It avoids filler, uses semicolons to pack related constraints efficiently, and every clause contributes unique information despite covering five actions in limited space.

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?

Given the tool's complexity (5 actions, 9 parameters, no output schema), the description covers all necessary facets: action-specific targets, permission restrictions, side effects on aggregates, and moderation workflow. The annotations and schema are rich, but the description fills in behavioral context that is essential for correct invocation, making it complete.

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 coverage is 100%, with each parameter already described in detail (e.g., 'create only', 'report only', null semantics for response). The description reinforces which parameters belong to which action but does not add new parameter-level meaning beyond what the schema already provides. Baseline 3 is appropriate given the schema's thoroughness.

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?

The description clearly identifies the tool as managing community reviews with five distinct actions (create, respond, report, remove, unhold), each with a specific verb and resource. It distinguishes itself from sibling tools by explicitly covering ratings, publisher responses, and moderation, leaving no ambiguity about its scope.

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 description provides explicit context for each action, including prerequisites (e.g., caller has installed the template for create, own template for respond, relay-operator status for remove/unhold) and constraints (one review per install, deduplication for report). It does not explicitly name alternative tools or state when not to use this tool, but the action-level guidance is strong and actionable.

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

All Homespun toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation4/5

Most tools are clearly distinct, with row operations (list, get, upsert, update, delete, restore) well separated. Some boundaries like apps vs deploy_app and credentials vs grants require careful reading, but descriptions resolve the overlap.

Naming Consistency2/5

Tool names mix resource nouns (apps, attachments, connections) with verb_noun actions (delete_row, deploy_app). Singular and plural forms are inconsistent, and there is no uniform pattern across the set.

Tool Count3/5

24 tools is on the heavy side, but the platform's breadth (app deployment, data, auth, community) justifies the count. Each tool has a distinct role, though the set slightly exceeds the typical well-scoped range.

Completeness4/5

The surface covers the full app lifecycle: deploy, manage, delete, row CRUD with restore, attachments, credentials, and community features. Minor gaps like no dedicated row search or outbound webhook management are workable via existing tools.

Resources