Skip to main content
Glama

DECA Labs

Ideas for your workspace

get_my_ideas
Read-only

The ideas DECA's engine wrote for your own workspace from what it knows about you (set in the dashboard under Settings → Your radar), each with why it is yours, and the day's public ideas it picked for you. Needs an API key; a key sees only its own workspace. Read only: it never asks the engine to write more. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_my_ideas"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many of each to return, 1 to 25. Default 10.
includeNoIdeas written for you, the day's picks for you, or both. Default both.all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description restates read-only rather than adding to it. It does add genuinely useful behavioral context beyond the annotations: an API key is required, a key sees only its own workspace, and the product is free. However, it says nothing about pagination, result ordering, or what happens when the personalized settings are empty.

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 content is compact at a few sentences, and the core payload (written ideas plus picks) is front-loaded. The parenthetical dashboard path is useful operational detail, though the long run-on opening sentence makes it slightly harder to scan than it needs to be.

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 two-optional-parameter read tool with no output schema, the description covers what is returned and the framing of each item ('each with why it is yours'), plus the auth scoping constraint. Missing only minor details such as ordering or empty-state behavior, which are low-impact here.

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%, so the schema already explains both limit and include fully. The description reinforces the meaning of the include values by describing 'written' ideas and 'the day's public ideas it picked' but adds no syntax, bounds, or interaction detail beyond the schema, 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?

The description uses specific language to name the resource and its two components: ideas the engine wrote for your workspace, plus the day's public picks, each with a rationale. It clearly distinguishes personal-workspace ideas from public picks, but never names the sibling get_ideas, so an agent cannot tell from this text alone how the two differ.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no alternative tool is named. The only selection context is implicit — that this is scoped to your own workspace and that personalization is configured in the dashboard — which does not tell an agent when to prefer it over get_ideas.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources