Skip to main content
Glama

vora_add_family_history

Add a family medical history entry to the signed-in user's Vora record.

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": {
      "relationship": "<relationship>",
      "conditionName": "<conditionName>"
    },
    "name": "vora_add_family_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNo
icdCodeNo
deceasedNo
ageAtOnsetNo
relationshipYes
conditionNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful context that the entry goes into the signed-in user's Vora record, but it does not disclose duplicate handling, validation behavior, or side effects.

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 is efficient, though its brevity is part of why the tool's parameters remain unexplained.

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

Completeness2/5

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

For a non-idempotent mutation with six parameters and no output schema, the description is too thin. It states the action but omits parameter meaning, required-field semantics, and behavioral details; the annotations cover safety but not enough to make the definition complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description provides no information about any of the six parameters. The required fields relationship and conditionName, as well as optional fields like notes, icdCode, deceased, and ageAtOnset, are left entirely to the schema names.

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 verb and resource: 'Add a family medical history entry' to the signed-in user's Vora record. It is clear what the tool does, but it does not explicitly differentiate this tool from sibling add tools such as vora_add_condition.

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 like vora_add_condition, nor any when-not conditions or prerequisites. The phrase 'family medical history' implies the use case, but the agent must infer it.

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