Skip to main content
Glama
ianderso

gramps-evidence-mcp

by ianderso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

add_url

Attach a web URL to a person, place, or repository in a Gramps Web family tree, specifying URL type and optional link description.

Instructions

Add a web URL to a person, place, or repository.

Only these three object types carry a URL list. For sources/citations, record a web address as an attribute (add_attribute) instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL, e.g. 'https://www.findagrave.com/memorial/123'.
targetYesHandle or gramps_id of the object.
url_typeNoURL type: 'Web Home', 'Web Search', 'E-mail', 'FTP', or a custom type the tree already has.Web Home
descriptionNoOptional link description.
object_typeYesType of the object: 'person', 'place', or 'repository' only.
allow_new_typeNoAccept a type that is neither a Gramps standard type nor one of the tree's custom types, creating it as a new custom type. Only when meant: a near-miss is refused with the closest names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.2.0
    • addedInput schema / properties / allow_new_type
      Added value: +{
+  "default": false,
+  "description": "Accept a type that is neither a Gramps standard type nor one of the tree's custom types, creating it as a new custom type. Only when meant: a near-miss is refused with the closest names.",
+  "type": "boolean"
+}
    • changedInput schema / properties / url_type / default
      Previous value: -"Web Home Page"New value: +"Web Home"
    • changedInput schema / properties / url_type / description
      Previous value: -"URL type, e.g. 'Web Home Page', 'Web Search', 'E-mail'."New value: +"URL type: 'Web Home', 'Web Search', 'E-mail', 'FTP', or a custom type the tree already has."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), so the bar is lower. The description adds real domain context not present in the annotations or schema: only these three object types carry a URL list. It stops short of saying what happens on a duplicate URL or how a rejected near-miss type surfaces, though the allow_new_type schema text covers the latter.

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 short sentences, zero filler, with the primary action stated first and the routing rule second. Every sentence earns its place.

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 6-parameter mutation tool with no output schema, the description covers target scope and alternative-tool routing, and all parameters are fully documented in the schema. It omits any indication of the return value or duplicate/upsert behavior, which is a minor gap given the annotations already convey the safety profile.

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%, including the object_type enum-ish restriction and the allow_new_type behavior, so the schema does the heavy lifting. The description reinforces the object_type constraint but adds no further syntax, defaults, or format guidance beyond what the properties already state. Baseline 3 is appropriate.

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?

States a specific verb ('Add') plus the resource ('a web URL') and constrains the valid targets to person, place, or repository. It also cites the sibling it is not (add_attribute) for sources/citations, so an agent can distinguish it without opening any schema.

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 gives the when ('person, place, or repository') and the when-not with a named alternative ('For sources/citations, record a web address as an attribute (add_attribute) instead'). Nothing about tool selection is left to inference for the source/citation case.

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