Viral Outliers

Create a Project

create_project

Creates an empty project with a name (1-80 characters) and optional notes, and returns its projectId and a link to it in the web app. Projects are free and unlimited on every plan. Fill it with add_project_posts. Cost: free.

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": "create_project"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Project name, 1-80 characters
`notes`	No	Optional notes, up to 500 characters

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent write, so the safety profile is covered. The description adds value beyond them by disclosing the return payload and the cost/quota behavior, but it is silent on duplicate-name handling and on whether the call fails or creates a second project.

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?

Front-loaded with the core action and result, then the follow-up tool. The closing "Cost: free" repeats the earlier "free and unlimited on every plan" sentence and is the one piece of waste in an otherwise tight two-sentence definition.

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?

For a two-parameter creation tool with no output schema, the description covers purpose, inputs, return values, cost, and the next step needed to make the project useful. Nothing an agent needs in order to call it correctly is missing.

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%, so both parameters are already documented by the schema. The description restates the 1-80 character name limit already present in the schema and reduces the notes bound (500 characters) to just "optional notes," adding no meaning beyond the structured fields. Baseline 3 applies.

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?

States a specific verb and resource ("Creates an empty project"), names the required field and its constraint, and enumerates what comes back (projectId plus web-app link). The mention of add_project_posts as the follow-up step separates it cleanly from the sibling tools that populate or delete projects.

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?

Gives clear forward guidance ("Fill it with add_project_posts") and addresses the main usage objection with "Projects are free and unlimited on every plan." It does not state explicit when-not-to-use conditions, such as what happens if a project with the same name already exists, which keeps it below a 5.

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

All Viral Outliers 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?