Skip to main content
Glama

Mockbird

by dev.workers.mockbird.mockbird
OverviewDiscussionsAdmin

add_resource

Add a resource (collection) to a project and seed it with realistic fake data. Either pass template (one of the built-ins, e.g. users, products, posts, comments, orders, todos, reviews, customers, events) or fields: an array of {name, type} where type ∈ uuid|firstName|lastName|fullName|username|email|avatar|image|word|words|title|sentence|paragraph|number|price|percent|boolean|date|pastDate|futureDate|url|domain|ip|phone|city|country|address|zipCode|company|jobTitle|color|latitude|longitude|rating|age|slug|status|category|refId, plus {name, type:"oneOf", values:[...]} for enums. seed = number of records to generate (default 20, max 100, 0 = empty). No project yet? Omit project AND adminKey and a fresh blank project is auto-created for this resource — the response then includes the new project id + adminKey (save both).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesResource name, plural (e.g. products).
seedNoRecords to seed (default 20, max 100).
fieldsNoArray of {name, type} (or {name, type:'oneOf', values:[…]}). Optional.
projectNoProject id. Omit (together with adminKey) to auto-create a fresh project.
adminKeyNoThe project's adminKey. Omit (together with project) to auto-create.
templateNoBuilt-in template name. Optional (use this OR fields).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / adminKey / description
      Previous value: -"The project's adminKey."New value: +"The project's adminKey. Omit (together with project) to auto-create."
    • changedInput schema / properties / project / description
      Previous value: -"Project id."New value: +"Project id. Omit (together with adminKey) to auto-create a fresh project."
    • changedInput schema / required
      Previous value: -[
-  "project",
-  "adminKey",
-  "name"
-]New value: +[
+  "name"
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses side effects such as auto-creating a project, the seeding behavior (default and max), and the response including new project credentials when auto-creating. It does not detail failure modes or reversibility, but covers key behavioral aspects.

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?

The description is dense but well-structured: it starts with the purpose, then explains the two modes, seed, and auto-creation. The list of field types is lengthy but necessary and directly actionable. No redundant sentences.

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 complex tool with 6 parameters and no output schema, the description covers the essential usage, including the auto-creation response. It does not explicitly describe the normal response format (e.g., resource id), but given the schema descriptions and the clarity of the operation, it is sufficiently complete for an agent to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds substantial meaning beyond the schema, especially for the 'fields' parameter by listing all valid types and the 'oneOf' enum structure. It also clarifies the seed defaults and the auto-creation condition for project/adminKey, which are not fully explained in 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?

The description clearly states the action: 'Add a resource (collection) to a project and seed it with realistic fake data.' It specifies the resource type and the dual modes (template or fields), which distinguishes it from siblings like generate_fake_data (which likely generates data without adding to a project).

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?

It explains when to use the tool, including the two input modes and the auto-creation behavior when no project exists. It gives conditional guidance (omit project and adminKey to auto-create) but does not explicitly mention alternatives like create_project or generate_fake_data, though the usage context is clear enough.

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

All Mockbird 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