Skip to main content
Glama
Sign In
seven-dpt-mcp

seven-dpt-mcp

by pierreb4
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Add a favorite problem

add_problem

Add a long-running problem to your persistent Feynman set, keeping the active set small to maintain focus across projects.

Instructions

Add a long-running problem to your global Feynman set — the ~dozen you keep dormant in mind across every project. Keep the active set small; that constraint is the method.

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": {
      "title": "<title>"
    },
    "name": "add_problem"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoFreeform tags, e.g. domains or project names
titleYesShort name for the problem
originNoWhere it came from (project, context)
statementNoFuller description / what 'solved' would look like

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses that the problem becomes part of a global set and that the set should be kept small. Does not cover idempotency or error handling, but is adequate for a simple additive operation.

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?

Two sentences, front-loaded with purpose and usage constraint. Every sentence adds value; no waste.

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?

Adequate for a creation tool with well-described schema. Covers purpose and usage constraint. No output schema, but return value not critical. Missing details like duplicate handling or error conditions.

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 describes all 4 parameters with full coverage (100%). Description adds no additional semantic meaning to individual parameters beyond the schema descriptions.

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?

Clear verb 'add' and resource 'problem to your global Feynman set'. Distinct from siblings like capture_spark (capture spark) and list_problems (list).

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?

States when to use: for long-running problems to keep in mind. Implies not for transient ideas. No explicit exclusions or alternatives named, but the constraint 'keep the active set small' provides guidance.

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

Deploy Server

Other Tools