Mockbird

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).

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Resource name, plural (e.g. products).
`seed`	No	Records to seed (default 20, max 100).
`fields`	No	Array of {name, type} (or {name, type:'oneOf', values:[…]}). Optional.
`project`	Yes	Project id.
`adminKey`	Yes	The project's adminKey.
`template`	No	Built-in template name. Optional (use this OR fields).

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description details key behaviors: seeding fake data, two configuration methods, and seed constraints. Does not mention error conditions or return values, but adequately covers the tool's operation.

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?

Four-sentence paragraph, front-loaded with purpose. Efficient but could be structured with bullet points for clarity. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, parameters, and usage, but lacks details on return values, error handling (e.g., resource already exists), or side effects. Adequate for a moderate-complexity tool with no output schema.

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

Parameters4/5

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

Schema coverage is 100%, baseline 3. Description enhances understanding by listing built-in templates, explaining fields structure with types, and clarifying seed defaults/max. Adds value beyond 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 explicitly states 'Add a resource (collection) to a project and seed it with realistic fake data', using specific verb and resource. It differentiates from siblings like 'import_data' and 'write_record' by focusing on seeding fake data.

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?

Describes when to use (add resource with fake data) and how to use via template or fields. Provides seed limits and defaults. Lacks explicit exclusions or alternative tool references.

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

All Mockbird tools Inspect

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.4/5.0

Disambiguation5/5

Each tool maps to a distinct resource/operation: project lifecycle, resource seeding, artifact import, record CRUD, custom routes, snapshots, request inspection, and external API status. Even the data-population tools are clearly separated by existing project (add_resource) versus new project (import_data/create_project).

Naming Consistency4/5

Most tools follow a clear verb_noun pattern (add_resource, create_project, query_records, write_record, delete_project, etc.). A few noun-style names (custom_route, project_info, snapshots) break the pattern, but all names are snake_case and readable.

Tool Count5/5

Eleven tools is a well-scoped set for a mock API server: project creation/deletion, data population/import, record operations, snapshots, custom routes, inspection, and API status all have dedicated tools without redundancy.

Completeness4/5

The core workflow is well covered: create/delete projects, add/import resources, CRUD records, snapshot state, define routes, and inspect requests. The main gaps are the lack of explicit resource deletion and custom-route update/delete, but these are workaroundable rather than blocking.

Resources

Need Help?