Skip to main content
Glama

Dayze — Life Context

Create Contact

create_person

Add a Dayze Contacts record, birthday included (YYYY-MM-DD, YYYY-MM, YYYY, or MM-DD if year unknown); checks duplicates first. An existing contact comes back unchanged with its person_id, not_applied (the fields you sent) and a hint. request_id is optional: without one, identical calls within 15 minutes return the first result. Advertised name create_person is stable; tools/call also accepts create_contact. ($0.10; API key required)

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

Input Schema

NameRequiredDescriptionDefault
nameYesDisplay name, e.g. Alex Chen.
tierNoRelationship priority: vip, normal or low, e.g. vip.
emailNoemail. Omit to leave unchanged; null or blank clears.
notesNoFree-text note, e.g. Follow up next week.
phoneNophone. Omit to leave unchanged; null or blank clears.
aliasesNoAlternate names stored as aliases, e.g. ["Lex","Alex C"].
companyNocompany. Omit to leave unchanged; null or blank clears.
walletsNoPHI-930: ENS (.eth) / SNS (.sol) names and/or addresses for this contact. Stored in social_handles (legacy ens/ens_address kept).
birthdayNoYYYY-MM-DD, YYYY-MM, YYYY, or MM-DD / --MM-DD when the year is unknown (same as update_person)
occupationNoOccupation / job title. Omit to leave unchanged; null or blank clears.
request_idNoClient idempotency key (retries return original result).
is_favoriteNoMark the contact as a favorite, e.g. true.
context_tagsNoContext tags such as Work, Personal or Family, e.g. ["Work"].
relationshipNoRelationship label, e.g. friend or sister.
relationshipsNoWho they are to the user, primary first, e.g. ["friend","colleague"].
idempotency_keyNoAlias for request_id.

Output Schema

NameRequiredDescriptionDefault
idNo
codeNo
hintNo
nameNo
slugNo
emailNo
phoneNo
peopleNo
personNoCRM person record.
accountNoThe Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
aliasesNoAliases saved on the new contact.
changedNo
companyNo
createdNo
messageNo
skippedNo
walletsNo
birthdayNoAs stored: YYYY-MM-DD. A year-unknown birthday is 1900-MM-DD (Feb 29: 1904-02-29).
duplicateNoTrue when the contact already existed: nothing on it was changed.
person_idNoThe new contact, or the existing one on a duplicate.
candidatesNo
created_atNo
occupationNo
person_idsNo
provenanceNoWhich connector wrote the record and which connected Dayze account received it.
inspect_urlNoThe Dayze page that shows the saved record.
matched_viaNo
not_appliedNoOn a duplicate: the fields sent that were not saved.
role_expandNo
inspect_noteNoWhat inspect_url opens. Never quote the record id.
hygiene_flagsNo
aliases_not_savedNoAliases not saved (another contact has them); the contact was still created.
idempotent_replayNo
birthday_precisionNoday, month, year, month_day (year unknown) or approximate.
needs_clarificationNoAsk which contact the user means; no contact was created or changed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changed
    • addedInput schema / properties / aliases / description
      Added value: +"Alternate names stored as aliases, e.g. [\"Lex\",\"Alex C\"]."
    • addedInput schema / properties / aliases / items / description
      Added value: +"Alias text, e.g. Lex."
    • addedInput schema / properties / context_tags / description
      Added value: +"Context tags such as Work, Personal or Family, e.g. [\"Work\"]."
    • addedInput schema / properties / context_tags / items / description
      Added value: +"Context tag, e.g. Work."
    • addedInput schema / properties / is_favorite / description
      Added value: +"Mark the contact as a favorite, e.g. true."
    • addedInput schema / properties / name / description
      Added value: +"Display name, e.g. Alex Chen."
    • addedInput schema / properties / notes / description
      Added value: +"Free-text note, e.g. Follow up next week."
    • addedInput schema / properties / relationship / description
      Added value: +"Relationship label, e.g. friend or sister."
    • addedInput schema / properties / relationships / description
      Added value: +"Who they are to the user, primary first, e.g. [\"friend\",\"colleague\"]."
    • addedInput schema / properties / relationships / items / description
      Added value: +"Relationship label, e.g. friend."
    • addedInput schema / properties / tier / description
      Added value: +"Relationship priority: vip, normal or low, e.g. vip."
    • addedInput schema / properties / wallets / items / description
      Added value: +"Wallet entry, e.g. {\"name\":\"zzuper.eth\",\"chain\":\"eth\"}."
    • addedInput schema / properties / wallets / items / properties / address / description
      Added value: +"Chain address, e.g. 0x5aAeb6053F3E94C9b9A09f33669435E7Ef1BeAed or a Solana pubkey."
    • addedInput schema / properties / wallets / items / properties / chain / description
      Added value: +"Chain id: eth, base or sol, e.g. eth."
    • addedInput schema / properties / wallets / items / properties / name / description
      Added value: +"ENS or SNS name, e.g. zzuper.eth."
  2. Changed13 schema fields changed
    • addedInput schema / properties / company
      Added value: +{
      +  "description": "company. Omit to leave unchanged; null or blank clears.",
      +  "maxLength": 200,
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / email / description
      Added value: +"email. Omit to leave unchanged; null or blank clears."
    • addedInput schema / properties / email / maxLength
      Added value: +254
    • changedInput schema / properties / email / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • addedInput schema / properties / occupation
      Added value: +{
      +  "description": "Occupation / job title. Omit to leave unchanged; null or blank clears.",
      +  "maxLength": 200,
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / phone / description
      Added value: +"phone. Omit to leave unchanged; null or blank clears."
    • addedInput schema / properties / phone / maxLength
      Added value: +64
    • changedInput schema / properties / phone / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • addedOutput schema / properties / changed
      Added value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
    • addedOutput schema / properties / company
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / email
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / occupation
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / phone
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  3. Changed2 schema fields changed
    • addedOutput schema / properties / inspect_note
      Added value: +{
      +  "description": "What inspect_url opens. Never quote the record id.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / inspect_url
      Added value: +{
      +  "description": "The Dayze page that shows the saved record.",
      +  "type": "string"
      +}
  4. Changed2 schema fields changed
    • addedOutput schema / properties / candidates
      Added value: +{
      +  "items": {
      +    "additionalProperties": true,
      +    "description": "Possible existing contacts, with person_id and name.",
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / needs_clarification
      Added value: +{
      +  "description": "Ask which contact the user means; no contact was created or changed.",
      +  "type": "boolean"
      +}
  5. Changed2 schema fields changed
    • addedInput schema / properties / wallets
      Added value: +{
      +  "description": "PHI-930: ENS (.eth) / SNS (.sol) names and/or addresses for this contact. Stored in social_handles (legacy ens/ens_address kept).",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "address": {
      +        "type": "string"
      +      },
      +      "chain": {
      +        "enum": [
      +          "eth",
      +          "base",
      +          "sol"
      +        ],
      +        "type": "string"
      +      },
      +      "name": {
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / wallets
      Added value: +{
      +  "items": {
      +    "additionalProperties": true,
      +    "description": "ENS/SNS wallet view: chain, name, address, resolution_status.",
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  6. Changed2 schema fields changed
    • addedOutput schema / properties / account
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.",
      +  "properties": {
      +    "display_name": {
      +      "description": "Account display name.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "handle": {
      +      "description": "Account handle, e.g. @goh.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "note": {
      +      "description": "How to disclose the account to the user.",
      +      "type": "string"
      +    },
      +    "qa_fixture": {
      +      "description": "True for a known QA test account: its records are fixture data, not a real life.",
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "handle",
      +    "display_name",
      +    "qa_fixture",
      +    "note"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / provenance
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Which connector wrote the record and which connected Dayze account received it.",
      +  "properties": {
      +    "account": {
      +      "additionalProperties": false,
      +      "description": "The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.",
      +      "properties": {
      +        "display_name": {
      +          "description": "Account display name.",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "handle": {
      +          "description": "Account handle, e.g. @goh.",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "note": {
      +          "description": "How to disclose the account to the user.",
      +          "type": "string"
      +        },
      +        "qa_fixture": {
      +          "description": "True for a known QA test account: its records are fixture data, not a real life.",
      +          "type": "boolean"
      +        }
      +      },
      +      "required": [
      +        "handle",
      +        "display_name",
      +        "qa_fixture",
      +        "note"
      +      ],
      +      "type": "object"
      +    },
      +    "channel": {
      +      "description": "Always mcp_connector.",
      +      "type": "string"
      +    },
      +    "connector": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "kind": {
      +          "description": "oauth or api_key.",
      +          "type": "string"
      +        },
      +        "name": {
      +          "description": "The connected app or API-key label shown to the account owner.",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "kind",
      +        "name"
      +      ],
      +      "type": "object"
      +    },
      +    "source": {
      +      "description": "chatgpt for ChatGPT OAuth writes; mcp for another OAuth app or API key.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "source",
      +    "channel",
      +    "connector",
      +    "account"
      +  ],
      +  "type": "object"
      +}
  7. Changed4 schema fields changed
    • addedOutput schema / properties / code
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / hygiene_flags
      Added value: +{
      +  "items": {
      +    "additionalProperties": true,
      +    "description": "Import hygiene skip/review flags.",
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / properties / message / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +"string"
    • addedOutput schema / properties / skipped
      Added value: +{
      +  "type": "boolean"
      +}
  8. Changed17 schema fields changed
    • addedOutput schema / properties / aliases
      Added value: +{
      +  "description": "Aliases saved on the new contact.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / aliases_not_saved
      Added value: +{
      +  "description": "Aliases not saved (another contact has them); the contact was still created.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "alias": {
      +        "type": "string"
      +      },
      +      "reason": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "alias",
      +      "reason"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / birthday
      Added value: +{
      +  "description": "As stored: YYYY-MM-DD. A year-unknown birthday is 1900-MM-DD (Feb 29: 1904-02-29).",
      +  "type": "string"
      +}
    • addedOutput schema / properties / birthday_precision
      Added value: +{
      +  "description": "day, month, year, month_day (year unknown) or approximate.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / created_at
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / duplicate
      Added value: +{
      +  "description": "True when the contact already existed: nothing on it was changed.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / hint
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / id
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / idempotent_replay
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / matched_via
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / name
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / not_applied
      Added value: +{
      +  "description": "On a duplicate: the fields sent that were not saved.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / people
      Added value: +{
      +  "items": {
      +    "additionalProperties": true,
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / person_id
      Added value: +{
      +  "description": "The new contact, or the existing one on a duplicate.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / person_ids
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / role_expand
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / slug
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  9. Changed3 schema fields changed
    • addedInput schema / properties / birthday
      Added value: +{
      +  "description": "YYYY-MM-DD, YYYY-MM, YYYY, or MM-DD / --MM-DD when the year is unknown (same as update_person)",
      +  "type": "string"
      +}
    • addedInput schema / properties / is_favorite
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / tier / enum
      Added value: +[
      +  "vip",
      +  "normal",
      +  "low"
      +]
  10. Changed2 schema fields changed
    • addedInput schema / properties / context_tags
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / relationships
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  11. Changed2 schema fields changed
    • addedInput schema / properties / idempotency_key
      Added value: +{
      +  "description": "Alias for request_id.",
      +  "type": "string"
      +}
    • addedInput schema / properties / request_id
      Added value: +{
      +  "description": "Client idempotency key (retries return original result).",
      +  "type": "string"
      +}
  12. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare that this writes, is closed-world and non-destructive; the description adds substantially beyond that with the pre-write duplicate check, the shape of the duplicate response (unchanged record, person_id, not_applied, hint), the 15-minute idempotency window, the $0.10 price, and the API key requirement. Those are exactly the mutation-side behaviors annotations cannot express, so this earns well above the baseline.

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?

Front-loads the core action and keeps the duplicate-response and idempotency details tight in two sentences. The trailing name-alias and pricing parentheticals are slightly tacked on, but each carries information an agent may need.

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?

For a 16-parameter mutation with an output schema, the description covers the remaining burdens: duplicate handling, retry semantics, cost, auth, and the duplicate-path return shape. Return-value documentation can be left to the output schema, so nothing an agent needs to call this correctly is missing.

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

Parameters5/5

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

Schema coverage is 100% so the baseline is 3, but the description adds genuine meaning on top: it explains that birthday accepts partial formats including MM-DD when the year is unknown, and it specifies the idempotency semantics of request_id (dedupe window and which result is returned). That goes beyond the field labels the schema already supplies.

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 and resource ("Add a Dayze Contacts record") and scopes it with the birthday/duplicate behavior, so an agent can tell this creates a person-level contact rather than a list or a contact method. It also disambiguates the advertised name from the create_contact alias, which is directly useful given the contacts-family siblings.

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

Usage Guidelines3/5

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

Gives real conditional guidance on request_id (without one, identical calls within 15 minutes return the first result), which tells an agent when to supply it. However, it never says when to prefer this over convert_contact_entity, add_person_contact_method, or create_contact_list, and there are no explicit exclusions or prerequisites beyond the API key note.

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.