Skip to main content
Glama
Mipiti
by Mipiti

get_functional_objectives

Retrieve a threat model's functional objectives (Given-When-Then test plans) as a list or by specific ID to review capability-condition test coverage and current test state.

Instructions

List a model's functional objectives, or fetch one by id. Read-only; no side effects.

A functional objective is a Capability × Condition test plan expressed as a Given-When-Then statement. functional_objective_id selects the behaviour:

  • omitted / empty string -> list every functional objective for the model (the full functional test plan).

  • a functional-objective id -> return just that one objective's detail, including its capability, condition, Given-When-Then statement, and current test state.

For pass/fail coverage state across all objectives use get_functional_coverage; for the actionable gaps use check_functional_gaps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
model_idYesID of the threat model whose functional objective(s) to read.
server_versionYes
functional_objective_idNoOptional. Omit (or pass "") to list every objective; pass an id (from a prior list call) to fetch that one.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

The description states 'Read-only; no side effects' which is a behavioral disclosure. Since no annotations are provided, this is valuable. It also explains the return behavior for list vs fetch modes, though it doesn't detail pagination or error cases. The read-only claim is explicit and helpful.

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?

The description is well-structured with a clear opening sentence, a definition paragraph, and a bullet-like list for parameter behavior. It is concise, front-loaded with the main purpose, and every sentence adds value. No fluff.

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?

Given the tool's moderate complexity (list vs fetch, with a domain-specific concept), the description is complete. It explains the domain concept (functional objective), the parameter behavior, and points to related tools. The output schema exists, so return values are not needed in the description. The description fully covers the tool's usage context.

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 67% (model_id and functional_objective_id have descriptions, server_version does not). The description adds meaning by explaining the functional_objective_id behavior in detail (omitted vs id) and defines what a functional objective is, which goes beyond the schema. It compensates for the undocumented server_version by not needing to explain it, but the description does not mention server_version at all, which is a minor gap.

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 clearly states the tool lists a model's functional objectives or fetches one by id, with a specific verb and resource. It distinguishes from siblings by naming get_functional_coverage and check_functional_gaps as alternatives for different needs.

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

Usage Guidelines5/5

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

Explicitly explains when to use this tool vs alternatives: for pass/fail coverage use get_functional_coverage, for actionable gaps use check_functional_gaps. Also clarifies the behavior based on functional_objective_id (omitted vs provided), giving clear context for selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Mipiti/mipiti-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server