More Good Reviews

Create Source

createSource

Create Source

Create a review source with a display name. The slug is generated from the name. Optional color and sprite class apply when no custom icon image is configured for this source.

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

Input Schema

Name	Required	Description
`name`	Yes	Display name for this source. Accepts at most 30 characters.
`color`	No	Hex color badge for this source. Accepts #RGB or #RRGGBB, at most 30 characters.
`sprite`	No	Font Awesome icon CSS classes for this source when no custom icon image is set. Font Awesome icon: two CSS class names as used with Font Awesome Web Fonts / classic CSS (not SVG/React props). Format is a style prefix (`fab`, `fad`, `fak`, `fal`, `far`, `fas`, or `fat`), one ASCII space, then an icon slug starting with `fa-` (lowercase letters and digits, hyphen-separated words). Examples: `fab fa-google`, `fas fa-star`. On write, omit, send null, or whitespace-only to clear. Font Awesome 6 semantic pairs such as `fa-solid fa-star` are not accepted; use `fas fa-star` instead. Accepts at most 50 characters.

Output Schema

Name	Required	Description
`code`	No	Short code or application-level status code for this resource.
`data`	No	Review source metadata.
`success`	No	Indicates whether the request completed successfully.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

changedInput schema / properties / color / description

Previous value: -"Hex color badge for this source. Accepts. Accepts at most 30 characters."New value: +"Hex color badge for this source. Accepts #RGB or #RRGGBB, at most 30 characters."

First observedSep 26, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare a non-read-only, non-idempotent, non-destructive open-world write, so the bar is lower. The description usefully adds that the slug is derived from the name and that color/sprite only take effect when no custom icon image exists on the source — behavior not visible in the schema. It stops short of noting collision/uniqueness handling or what happens when a duplicate name is submitted.

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 short sentences, front-loaded with the action, and every clause carries information. The only waste is the 'Create Source' heading, which merely restates the tool title.

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?

An output schema exists, so return values need not be described, and parameters are fully documented in the schema. For a simple three-parameter create tool, the description covers the creation semantics, the derived slug, and the conditional fields without leaving an agent unable to invoke it correctly.

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% and the parameter descriptions are unusually thorough (length limits, hex formats, Font Awesome class grammar), so the schema carries the load and the baseline is 3. The description adds only the derived-slug relationship and the conditional applicability of color/sprite, not new syntax or format guidance.

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 and resource: 'Create a review source with a display name.' The resource ('review source') is distinct from the other create* siblings (createIcon, createTag, createReview, createLocation). However, it never explicitly routes the agent away from those siblings or clarifies the relationship to updateSource/listSources.

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?

There is no stated when-to-use, when-not-to-use, or named alternative; the agent must infer from the tool name that this is the creation path for sources. The one conditional clause ('color and sprite class apply when no custom icon image is configured') gives partial usage context but is about field applicability rather than tool selection.

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

All More Good Reviews tools Inspect

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

Need Help?