Skip to main content
Glama
adityarya24

Astro Skill MCP Server

by adityarya24
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

Save Client Profile

save_client_profile
DestructiveIdempotent

Upsert a client profile with client_id, display name, notes, and optional birth details including date, time, place, coordinates, and timezone. Returns saved profile.

Instructions

Create or update (upsert by client_id) a client profile in the SQLite store, optionally with birth details. Returns the saved profile.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
db_pathNoPath of the SQLite client store (default: data/astro_mcp.sqlite3). Must resolve inside the server working directory, the system temp directory, or ASTRO_MCP_BASE_DIR; other paths are rejected.
profileYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Addedv1.1.1
  2. Removedv1.1.0
  3. Changed1 schema field changedv1.1.0
    • changedInput schema / properties / db_path / description
      Previous value: -"Path of the SQLite client store (default: data/astro_mcp.sqlite3)."New value: +"Path of the SQLite client store (default: data/astro_mcp.sqlite3). Must resolve inside the server working directory, the system temp directory, or ASTRO_MCP_BASE_DIR; other paths are rejected."
  4. Changed6 schema fields changedv1.0.1
    • addedInput schema / properties / db_path / description
      Added value: +"Path of the SQLite client store (default: data/astro_mcp.sqlite3)."
    • changedInput schema / properties / profile / properties / birth / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "dob": {
-        "description": "DD/MM/YYYY or YYYY-MM-DD",
-        "type": "string"
-      },
-      "lat": {
-        "type": "number"
-      },
-      "lon": {
-        "type": "number"
-      },
-      "place": {
-        "type": "string"
-      },
-      "timezone_name": {
-        "description": "IANA name, eg Asia/Kolkata",
-        "type": "string"
-      },
-      "tob": {
-        "description": "HH:MM (24h) local time",
-        "type": "string"
-      }
-    },
-    "required": [
-      "dob",
-      "tob",
-      "place",
-      "lat",
-      "lon",
-      "timezone_name"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "dob": {
+        "description": "Date of birth, DD/MM/YYYY or YYYY-MM-DD.",
+        "type": "string"
+      },
+      "lat": {
+        "description": "Latitude of the birth place in decimal degrees (north positive).",
+        "type": "number"
+      },
+      "lon": {
+        "description": "Longitude of the birth place in decimal degrees (east positive).",
+        "type": "number"
+      },
+      "place": {
+        "description": "Birth place name; a label for output, not geocoded.",
+        "type": "string"
+      },
+      "timezone_name": {
+        "description": "IANA timezone of the birth place, e.g. Asia/Kolkata.",
+        "type": "string"
+      },
+      "tob": {
+        "description": "Time of birth, HH:MM (24-hour clock), local time at the birth place.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "dob",
+      "tob",
+      "place",
+      "lat",
+      "lon",
+      "timezone_name"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / profile / properties / birth / description
      Added value: +"Birth details to store with the profile."
    • addedInput schema / properties / profile / properties / client_id / description
      Added value: +"Stable unique identifier for the client."
    • addedInput schema / properties / profile / properties / display_name / description
      Added value: +"Human-readable client name."
    • addedInput schema / properties / profile / properties / notes / description
      Added value: +"Free-form notes about the client."
  5. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations indicate destructiveHint=true and idempotentHint=true, and the description confirms upsert behavior and return of saved profile. However, it does not elaborate on what destructive actions occur (e.g., overwriting existing data) or any rate limits.

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 a single sentence that covers key aspects (upsert, storage, optional birth details, return value) without any redundant or vague language.

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?

The description covers the essential behavior and return value, but lacks details on the format of the returned profile or handling of the db_path parameter. Given the absence of an output schema, a bit more detail on the return value would be helpful.

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 coverage is 50%, and the description adds little beyond the schema: it mentions 'optionally with birth details' and implies db_path usage but does not describe parameter formats or constraints not already in the schema.

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 explicitly states it performs an upsert (create or update) on a client profile in the SQLite store, with optional birth details, and returns the saved profile. This clearly distinguishes it from sibling tools like parse_birth_details or calculation tools.

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?

The description mentions the upsert behavior and optional birth details but provides no explicit guidance on when to use this tool versus siblings like parse_birth_details or when not to use it.

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/adityarya24/astro-skill'

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