Figs, Relationship Expert

Name the dance: the pattern in your conflict

name_conflict_pattern

Read-onlyIdempotent

Describe a recent conflict and understand the repeating pattern, what each person protects and fears, and what disconnection is like for each of you.

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": {
      "what_happened": "<what_happened>"
    },
    "name": "name_conflict_pattern"
  }
}

Input Schema

Name	Required	Description	Default
`what_happened`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 23, 2026
- removedInput schema / properties / what_happened / maxLength
```
Removed value: -12000
```
- removedInput schema / properties / what_happened / minLength
```
Removed value: -3
```
AddedOct 1, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, covering the safety profile. The description adds useful analytical context about what the tool will surface, but it does not describe operational behavior such as privacy, data retention, or response format.

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 description is a single, front-loaded sentence with no wasted words. It could be slightly more structured by separating input expectations from output analysis, but it is efficient and readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter tool with annotations and no output schema, the description adequately covers what the tool does. However, given several sibling relationship tools, it lacks routing guidance and does not clarify when this specific pattern-analysis tool is the right choice.

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?

The schema has zero description coverage for the single required parameter 'what_happened'. The description compensates by indicating the input should be a narrative of a recent conflict, but it does not specify length, detail level, or what emotional or factual elements to include.

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 states a specific action (describe a recent conflict) and a concrete analytical outcome (repeating pattern, what each person protects and fears, disconnection experience). It is clear what the tool does, but it does not distinguish itself from siblings like repair_right_now or ask_relationship_expert.

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 explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. The phrase 'describe a recent conflict' implies an input context but does not help an agent choose between this and sibling tools.

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

All Figs, Relationship Expert 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?