worklore

suggest_for_project

Read-only

Given a short description of the current project (stack, what you're building, recent problems), suggest up to 3 worklore stories worth reproducing here, with why each fits and its tier.

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

Input Schema

Name	Required	Description	Default
`context`	Yes	Project context: stack, goal, recent TODOs/problems.

Output Schema

Name	Required	Description	Default
`note`	No
`suggested`	Yes
`about_tiers`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 15, 2026

changedOutput schema / properties / suggested / items / properties / capability / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "pattern": "^T[0-4] · ",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / suggested / items / properties / tier / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "T0",
+      "T1",
+      "T2",
+      "T3",
+      "T4"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / suggested / items / properties / visibility

Added value: +{
+  "enum": [
+    "public",
+    "private"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / suggested / items / properties / why / minLength
```
Added value: +1
```
addedOutput schema / properties / suggested / maxItems
```
Added value: +3
```

First observedOct 6, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful shape information (bounded to 3 results, each with a fit rationale and tier), but says nothing about determinism, ranking basis, or behavior when no story fits.

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?

One sentence, zero filler, with the input condition front-loaded ahead of the output contract. Nothing is repeated or padded.

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?

With a 100%-covered single parameter, an output schema carrying return structure, and annotations covering the safety profile, the description supplies what is still needed: the result count cap and that each suggestion includes a fit rationale and tier. Only minor gaps remain around ranking or empty-result behavior.

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 there is only one parameter, whose schema text already spells out 'stack, goal, recent TODOs/problems'. The description's 'stack, what you're building, recent problems' is a near-verbatim restatement rather than added semantics, so the baseline 3 applies.

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?

Specific verb (suggest) plus resource (worklore stories) and a clear scope qualifier (up to 3, based on a project description, with rationale and tier). It reads distinctly from siblings like search_stories or get_story, but never names an alternative to anchor the distinction.

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?

The trigger condition is implied clearly ('given a short description of the current project'), so an agent can infer when this fits. However, there is no explicit when-not guidance and no named alternative such as search_stories for agents who already know what they want.

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

All worklore 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.